Skip to main content
Glama

Update the Store listing

update_listing
DestructiveIdempotent

Saves changes to the Store listing as a draft; nothing goes to Microsoft until send_listing_update or the next submit_update. Pass languages as { "en-us": { "description": "..." } } with only the fields to change: title (a name reserved in Partner Center), shortDescription (up to 1000, about 270 shown), description (up to 10,000), features (up to 20 of 200, no bullets), keywords (search terms, up to 7 of 40 and 21 words in total). Lists replace the whole list; a field set back to its live text stops being a change. addLanguages adds Store languages (they need a description and get a copy of the English screenshots; translate_listing_missing fills their text and captions), removeLanguages removes languages added in the draft. certNotes replaces the notes for certification, which go out with every submission. Returns the listing overview with its problems.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appId": "<appId>"
    },
    "name": "update_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesThe app id from list_apps.
certNotesNoNotes for certification for Microsoft's testers. An empty string clears them.
languagesNoFields to change per language code.
addLanguagesNoStore language codes to add, like fr-fr or ja.
removeLanguagesNoLanguages added in the draft to take out again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing that writes land only in the draft, that list fields replace rather than merge, that reverting a field to its live text cancels the change, and that certNotes ship with every submission. It stops short of stating that draft state itself can be lost, which is what the destructiveHint on this tool arguably warns about.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single dense paragraph is front-loaded correctly, leading with the draft-only behavior before field details. It is a wall of semicolon-joined clauses, though, so field-limit details are harder to scan than they need to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter nested-object mutation with no output schema, the description covers everything an agent needs: draft versus live lifecycle, replacement semantics, per-field limits, language add/remove rules, and a note that the return is the listing overview with its problems. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the description still adds real meaning: title is a name reserved in Partner Center, description caps at 10,000 with about 270 characters shown, features take no bullets, keywords are limited to 21 words total, and new languages need a description plus a copy of the English screenshots. It documents list-replacement semantics that the schema's array types cannot express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Saves changes to the Store listing') with an explicit scope qualifier ('as a draft'), and immediately names the tools that actually publish (send_listing_update, submit_update). An agent can distinguish this from discard_listing_changes or submit_update without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the decisive when-to-use rule: nothing reaches Microsoft until send_listing_update or the next submit_update. It also routes related work to siblings by name — translate_listing_missing for filling translated text and captions — and explains that adding/removing languages is done through this same call rather than a separate tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources