Skip to main content
Glama
Sign In
OutreachPilot MCP Server

OutreachPilot MCP Server

by emielmadonna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

check_research_status

Check the status of a research job, get result count, and retrieve full results once complete. Poll repeatedly until status is 'complete'.

Instructions

Poll the status of a running research job. Returns status (pending/running/complete/error), result count, and full results when complete. Keep calling this until status is 'complete', then call import_research_results.

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

Input Schema

NameRequiredDescriptionDefault
job_idYesResearch job ID from run_research.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are present, so the description carries the burden. It discloses the return statuses, result count, full results on completion, and the polling behavior. This is transparent for a simple poller, though it omits edge cases like invalid job IDs or error handling details.

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?

Two sentences, front-loaded with an action verb and concise details on returns and workflow. No filler or redundant information.

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?

Since there is no output schema, the description explains what the tool returns (status, result count, full results) and delineates the polling loop and subsequent tool to call. This is complete for a single-parameter tool.

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?

Schema coverage is 100% (job_id described as 'Research job ID from run_research'). The description adds context about the polling loop but does not add new parameter details beyond what the schema already provides, so the baseline score of 3 applies.

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?

The description clearly states the tool polls the status of a running research job, listing specific statuses and return values. It distinguishes itself from sibling tools like import_research_results by framing the polling action and what to do after.

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?

Provides explicit guidance: 'Keep calling this until status is complete, then call import_research_results.' This tells when and how to use it in the workflow, though it does not mention when not to use or alternatives.

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

Deploy Server

Other Tools