Skip to main content
Glama

Get keyword research status

get_keyword_research_status
Read-onlyIdempotent

Status and progress of a keyword research run (queued, running, done, partial, failed; done with limited: true is complete (limited): a country used its whole store-request budget), without the full result; without run_id, the workspace's recent runs. Read-only; spends nothing.

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_keyword_research_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNoRun id from start_keyword_research.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: "spends nothing" (no credit consumption) and the semantics of "done with limited: true" as a completed-but-budget-exhausted state. It does not cover polling behavior or how fresh an in-progress status is, which keeps it off a 5.

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?

One sentence, front-loaded with the core purpose and status values, with the default-behavior clause placed after. The nested parentheses around the limited-budget explanation are dense and slightly harder to parse, but no sentence 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?

With no output schema, the description carries the burden of describing returns and does so by naming the status set and the progress notion. Minor gaps remain on the shape of progress reporting and whether the recent-runs fallback is bounded, but an agent can call it correctly as written.

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% and the single parameter is already documented as "Run id from start_keyword_research." The description still adds meaning by explaining what happens when the parameter is omitted (falls back to recent workspace runs), which the schema does not state.

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 ("Status and progress of a keyword research run") and explicitly bounds the scope with "without the full result," which separates it from the results-oriented siblings. The parenthetical enumerates the exact status values, so an agent knows what this tool reports.

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 a clear usage rule for the optional parameter: "without run_id, the workspace's recent runs." The phrase "without the full result" implicitly routes agents to the results tool for payloads, but no sibling is named explicitly, so routing still requires an inference.

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