Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

check_job_status

Read-onlyIdempotent

Check a SupaBird tool call that was still running. Tools such as search_tweets, schedule_post, cross_post, the write_* tools, learn_creator_style and the analytics reports return { status: "running", job_id } when they need more than ~20 seconds. If status is 'running': tell the user it's still working and call this tool again in about 10 seconds with the same job_id. Do not call the original tool again. If status is 'completed' or 'failed': the response is the original tool's result. Present it exactly as that tool's instructions say.

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": {
      "job_id": "<job_id>"
    },
    "name": "check_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id returned with status 'running'.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description still adds real behavior: the ~20 second threshold that triggers job creation, the ~10 second polling cadence, the no-retry-original rule, and the semantics of what the payload means once terminal. That is context an agent cannot get from the structured fields.

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

Conciseness5/5

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

Three short, front-loaded blocks: what the tool is, what to do on a non-terminal status, what to do on a terminal status. The conditional framing mirrors the agent's decision tree and there is no filler.

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?

No output schema exists, and the description compensates by explaining that the return value is the original tool's result and should be presented per that tool's instructions. Combined with the polling rules, an agent has everything needed to call this correctly in a loop.

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

Parameters3/5

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

There is one parameter at 100% schema description coverage, and the schema already states job_id is the value returned with status 'running'. The description reinforces that the same job_id must be reused across polls, but adds only marginal meaning beyond the schema, which is the baseline-3 case.

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 ('Check a SupaBird tool call that was still running') and immediately scopes it by naming the exact tools that produce the running state (search_tweets, schedule_post, cross_post, write_*, learn_creator_style, analytics reports). An agent can distinguish this from the originating tools without opening any 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 explicit branching guidance: on 'running', inform the user and re-poll with the same job_id in ~10s; explicitly prohibits re-invoking the original tool; on 'completed'/'failed', treat the response as the original tool's result. This is exactly the when/when-not/alternative coverage the dimension asks for.

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

All SupaBird toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources