Mobile Joe

Read the original alert, current revision, targeting, actual stored translations and the versions the app's devices have reported. Missing locales are absent, never replaced with fallback text.

get_alert

Read a feature plan with its status, votes and current revision.

get_feature_plan

List or search original FAQ content and stored translations, including drafts and archives. Results use ID pagination; position gives display order.

list_faqs

List or search original alert content, targeting and stored translations, including drafts and archives. Results use ID pagination.

list_alerts

List authorized apps and their settings. Use the returned app ID in the other tools. source_language is the locale of the original FAQ text, so translations use other locales; regional variants of it such as en-GB are allowed.

list_apps

List or search feature plans, including hidden drafts. Check existing plans for overlap before proposing, creating or changing a plan. A query matches plans whose original text or a translation contains all of its words, so a match may show only in translations; also search single key terms or list without a query. Results use ID pagination.

list_feature_plans

Merge a duplicate feature plan into another plan of the same app only when the developer explicitly asks. Votes from app users move to the remaining plan, an app user who voted for both counts once, and initial votes are added up. The merged plan is permanently deleted; the remaining plan keeps its title, body and status. If both plans have different statuses, ask the developer which status the remaining plan should have before merging and set it afterwards with set_feature_plan_status. Suggest updating its wording afterwards if the merged plan adds something. Requires feature_plans:publish if either plan is visible.

merge_feature_plan

Move a FAQ to a one-based position. Read its current revision first. Requires faqs:write and faqs:publish because other published entries may move.

move_faq

Publish a FAQ and its stored translations only when the user explicitly asks. Requires faqs:write and faqs:publish.

publish_faq

Remove only the specified locale. Read first. Published content requires faqs:publish.

remove_faq_translation

Remove only the specified locale from an alert. Read first. Delivered alerts and drafts in debug delivery require alerts:publish.

remove_alert_translation

Remove only the specified locale from a feature plan. Read first. Visible plans require feature_plans:publish.

remove_feature_plan_translation

Return a FAQ to draft, removing it from SDK delivery. Requires faqs:publish if currently published.

draft_faq

Return an alert to draft, removing it from SDK delivery. Requires alerts:publish if currently delivered or a draft in debug delivery.

draft_alert

Add or replace the translation for exactly one locale, preserving other locales. Prefer language codes such as pt; they serve every region. Use a regional locale such as pt-BR only for content that differs by region. The app's source_language holds the original text; change it with update_faq. Regional variants of it such as en-GB are allowed. Read first. Published content requires faqs:publish.

put_faq_translation

Add or replace the alert translation for exactly one locale, preserving other locales. Prefer language codes such as pt; they serve every region. Use a regional locale such as pt-BR only for content that differs by region. The app's source_language holds the original text; change it with update_alert. Read first. Delivered alerts and drafts in debug delivery require alerts:publish.

put_alert_translation

Add or replace the feature plan translation for exactly one locale, preserving other locales. Translate the plan's current title and body faithfully; change the wording with update_feature_plan. Prefer language codes such as pt; they serve every region. Use a regional locale such as pt-BR only for content that differs by region. The app's source_language holds the original text. Read first. Visible plans require feature_plans:publish.

put_feature_plan_translation

Replace who receives an alert. broadcast reaches every app user and clears the filter. filtered reaches only iOS or Android devices whose platform has versions listed: a device matches when its app version and OS version appear in its platform's lists; an empty list accepts any version of that kind. Omitted lists are cleared. Use exact values from reported_versions in get_alert. Read first. Delivered alerts and drafts in debug delivery require alerts:publish.

set_alert_targeting

Change a feature plan's status only when the developer explicitly asks. Every status except draft makes the plan visible to app users and open for votes; draft hides it and keeps its votes. under_review, planned and in_progress form the roadmap; closed marks a declined plan. Requires feature_plans:write and feature_plans:publish.

set_feature_plan_status

Replace original FAQ title and body, preserving translations. Read first. Changing published content also requires faqs:publish.

update_faq

Replace original alert title, message and kind, preserving translations and targeting. occurred_at stays unchanged when omitted. Read first. Changing a delivered alert or a draft in debug delivery also requires alerts:publish.

update_alert

Change app settings only when the developer explicitly asks. Pass only the settings to change; null clears a URL. A new website URL refetches the app icon. Requires apps:write.

update_app

Replace a feature plan's title and body and optionally its initial votes. Read it first and check other plans for overlap. Describe the product outcome in the developer's language rather than copying requests from app users, and get the developer's agreement on the wording before changing it. Change initial_votes only when the developer explicitly asks; omit it to keep the current value. Votes from app users are kept. Changing a visible plan requires feature_plans:publish and is immediately visible to app users.

update_feature_plan