Skip to main content
Glama
telegram-keyword-search

telegram-keyword-search

get_keyword_results

Retrieve posts from an existing Telegram keyword search by run_id, waiting up to 45 seconds for completion; call again with the same run_id while the search is still running.

Instructions

Get the posts found by a search started with start_keyword_search. Step 2 of 2. Reading results is free; it never starts a new search.

Waits up to wait_secs for the search to finish. Returns {"finished", "status", "posts",
"message"}. If "finished" is false the search is still running and "posts" is empty:
call get_keyword_results again with the same run_id (do not start a new search).

Args:
    run_id: the run_id returned by start_keyword_search.
    wait_secs: how long to wait for the search to finish, 0-45 seconds.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_keyword_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
wait_secsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses cost ("Reading results is free"), that it is non-mutating ("never starts a new search"), the blocking behavior (waits up to wait_secs), and what an unfinished search returns (empty posts). That is unusually complete behavioral disclosure for a polling tool.

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?

Front-loads what the tool is and its two-step position, then the wait semantics, then the return shape, with the polling instruction placed exactly where a caller needs it. The Args block is short and adds value the 0%-coverage schema lacks rather than restating it.

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, so the description enumerates the return keys ("finished", "status", "posts", "message") and explains the key failure mode (finished=false implies empty posts). For a two-parameter polling tool this is enough to call it correctly, including on retries.

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 0%, so the description must compensate, and it does: run_id is defined by origin ("the run_id returned by start_keyword_search") and wait_secs gets a meaningful range ("0-45 seconds"). It omits the default of 40 that the schema declares, so it does not fully cover both parameters.

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 posts found by a search") and anchors it to the lifecycle ("Step 2 of 2") started by start_keyword_search, so an agent can place it relative to the sibling without opening the 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 (after start_keyword_search), an explicit loop rule ("call get_keyword_results again with the same run_id"), and an explicit prohibition ("do not start a new search"). It also names start_keyword_search as the originating alternative, leaving nothing to infer.

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