Skip to main content
Glama

Get update status

get_update_status
Read-only

Where an update stands. Pass appId for the app's latest update, or releaseId for one update. Returns the version live in the Store, the update's status (uploading, uploaded, submitting, submitted, failed, canceled), its error, and once it's submitted, partnerCenterUrl and Partner Center's certification status and errors. certification.waitingForYou means it passed certification and waits for the person to press Publish now in Partner Center, and certification.publishDate is when one set to publish on a date starts publishing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_update_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdNoThe app id from list_apps.
releaseIdNoA releaseId from start_update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe read-only, non-destructive, closed-world operation. The description adds substantial behavioral detail beyond annotations: the possible update statuses, returned error information, Partner Center fields, and certification semantics such as waitingForYou and publishDate.

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 description is front-loaded with the core purpose and then explains parameter choice and return semantics. The certification explanation is lengthy but earns its place because there is no output schema to document those fields.

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

Completeness4/5

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

For a two-parameter, read-only status tool with no output schema, the description is complete enough: it covers the main return fields and status meanings. The main remaining gap is the lack of guidance on mutual exclusivity and default behavior when neither identifier is provided.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3. The description adds meaningful semantics by clarifying that appId returns the app's latest update while releaseId returns one specific update, though it leaves precedence undefined when both are supplied.

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

Purpose4/5

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

The description clearly communicates that this tool reports where an update stands, and the parameter-selection sentence reinforces the specific resource. It does not explicitly name sibling tools such as start_update or submit_update, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

It explains which identifier to pass for the latest app update versus a specific update, which gives useful invocation context. However, it does not state when to prefer this over related siblings or what happens if both or neither parameter is supplied.

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