Skip to main content
Glama

Poll an AdGPT async job

adgpt_job
Read-only

Poll a long-running generation to completion. Pass the status operationId (from a create call's job handle) and its params (e.g. {id}). Waits up to waitSeconds (max 25); if not finished, returns callAgain=true — invoke again to keep waiting. Never charges credits.

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": {
      "operationId": "<operationId>"
    },
    "name": "adgpt_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoPath/query params for the status op, e.g. {id: 123}.
operationIdYesThe status operation to poll, e.g. full-campaign.status.
waitSecondsNoMax seconds to block this call (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true; the description adds three distinct behavioral facts beyond that: the call blocks up to waitSeconds (max 25), a not-yet-finished job is signalled via callAgain=true rather than an error, and polling never consumes credits. These are exactly the traits an agent needs to drive a polling loop safely and cheaply.

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?

Front-loads purpose, then instructions, then the cost reassurance, with no filler sentences. Minor overlap with the schema (the max-25 bound and the {id} example appear in both), but nothing is wasted.

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?

Covers the control flow of a blocking poll loop well, which is the hard part for a tool with a nested params object and no output schema. It leaves the shape of a completed job's payload and the failure-state signal unstated, a real gap given there is no output schema to fall back on.

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 100%, so the baseline is 3; the description earns above baseline by explaining provenance for operationId ('from a create call's job handle') and tying params to the status operation, which the schema does not convey. The waitSeconds and {id} examples largely repeat schema text.

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 ('Poll a long-running generation to completion') and frames it relative to the create call that produced the job handle. No sibling tool in the list performs polling, so there is nothing to confuse it with, and an agent can identify the tool from the first sentence alone.

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

Usage Guidelines4/5

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

Gives clear when-to-use context (after a create call returns a job handle) plus an explicit continuation rule: if callAgain=true, invoke again to keep waiting. It does not spell out what to do on a failed job or state when not to use it, so it stops short of full alternative/exclusion guidance.

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