Skip to main content
Glama
Sign In
olostep-mcp

olostep-mcp

by olostep
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Batch Results

get_batch_results
Read-onlyIdempotent

Retrieve batch scrape results by batch_id: check in-progress status, then fetch paginated URL titles and content when the batch completes.

Instructions

Use this to get the content of a batch started with batch_scrape_urls, using its batch_id. While the batch is in_progress it returns the status: call again in about 10 seconds. Once completed it returns each URL's url, title and content, up to items_limit per call; when has_more is true, pass next_cursor for the rest. Do not start a new batch to check on one that is still running.

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": {
      "batch_id": "<batch_id>"
    },
    "name": "get_batch_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor. Pass next_cursor from the previous result to get the next pages. Default: 0 (first page).
formatsNoContent formats to retrieve per URL. Default: ["markdown"].
batch_idYesThe batch_id (or id) returned from batch_scrape_urls.
items_limitNoMax number of items to retrieve content for per call (1-100). Default: 20.
max_charactersNoMax characters of content per URL (default 20000). Longer pages are cut and link to their full text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.21

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is low, yet the description still adds real behavioral context: the in_progress state returns a status and should be re-polled, completion returns url/title/content per URL, and partial results are signaled by has_more. That state-machine detail is not derivable from the annotations or schema.

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?

Four short sentences, front-loaded with purpose, then polling behavior, then return shape, then a closing caution. No filler and every sentence carries a distinct operational fact.

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?

There is no output schema, but the description compensates by naming the returned fields and the pagination signal, and it explains the asynchronous polling contract that an agent would otherwise have to guess. For a 5-parameter read tool this covers everything needed to call it correctly.

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%, so the schema already documents batch_id, cursor, formats, items_limit and max_characters, giving a baseline of 3. The description only reinforces items_limit and the pagination token, and it refers to 'next_cursor' while the actual parameter is named 'cursor' — a naming mismatch that slightly undercuts the value it adds.

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 ('get the content of a batch') and ties it to the sibling that produces the identifier ('started with batch_scrape_urls'). An agent can distinguish this retrieval tool from batch_scrape_urls without opening either 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 when-to-use ('get the content of a batch started with batch_scrape_urls') plus a when-not-to: 'Do not start a new batch to check on one that is still running.' It even specifies the polling cadence ('call again in about 10 seconds'), leaving little to inference.

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