Skip to main content
Glama

Get a push job

get_sync_job
Read-onlyIdempotent

Read a push job’s completion state and what it did: locales lists, per store and locale, the fields the store accepted (updated), status ok / partial / failed / skipped and each error as the store's code and detail; errors and warnings hold job-level messages. Raw provider logs are omitted. A job whose function was cut is reported FAILED once it stops progressing (10 minutes), never RUNNING forever; pushing again resumes it without re-sending screenshots already on the store.

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": {
      "jobId": "<jobId>"
    },
    "name": "get_sync_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

With annotations already declaring readOnly/idempotent/non-destructive, the description still adds substantial behavior: raw provider logs are omitted, a stalled job is forced to FAILED after 10 minutes rather than staying RUNNING, and re-pushing resumes without re-sending existing screenshots. These are exactly the operational traits an agent cannot infer from the schema or annotations.

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 purpose is front-loaded and every clause carries information (status vocabulary, error shape, timeout behavior, resume semantics). It is dense and the semicolon-chained sentences run long, but nothing is filler.

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?

There is no output schema, so the description must describe the return payload — and it does, covering the status enum, per-store/per-locale results, error objects, and job-level messages. The one real gap is the jobId argument's origin, which leaves an agent unsure how to obtain a valid ID.

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

Parameters2/5

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

Schema description coverage is 0% and the single jobId parameter has no documentation in either the schema or the description — nothing on where the ID comes from, its format, or what happens with an unknown/stale ID. The description only refers to "a push job" in passing, so it does not compensate for the coverage gap.

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 opens with a specific verb and resource: "Read a push job's completion state and what it did," then enumerates the returned data (locales, per-store accepted fields, status values, errors/warnings). That is far more specific than the title alone. No sibling tool returns push-job state, so differentiation is implicit rather than stated.

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?

Usage is only implied: the mention of "completion state" and of "pushing again resumes it" tells an agent this is a poll-after-push tool, but it never says when to call it, how often to poll, or what to do instead if the job is still running. No alternative tool is named.

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