Skip to main content
Glama

GTM Daily

Search GTM launches

search_gtm_launches
Read-onlyIdempotent

Launches that have actually opened (live or closed), with real vote counts. Scheduled launches are not listed.

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": "search_gtm_launches"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
sortNo
limitNoMax results (default 10, max 50).
cursorNoOpaque cursor from a previous result's next_cursor.
windowNo

Output Schema

NameRequiredDescriptionDefault
okNo
codeNo
dataNo
statusYes
messageNo
warningsNo
next_stepNo
next_cursorNo
action_grantNo
approval_urlNo
correlation_idYes
missing_fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds real behavioral value by constraining the result set to opened launches and asserting vote counts are real, but it says nothing about pagination (the cursor/limit behavior) or the cost/size of queries.

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?

Two short sentences with no filler, and the scope constraint leads. It is efficient but slightly backwards in structure — it opens with the result set rather than stating that this is a search over launches, which would orient the agent faster.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values needn't be explained, and annotations cover safety. The remaining gap is functional: with 5 optional parameters and 40% schema coverage, the description should explain how date/sort/window interact with the opened-launches scope, and it does not.

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

Parameters2/5

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

Schema coverage is only 40%: limit and cursor are documented in the schema, but date, sort (trending/newest/top/picks) and window (today/week/all) carry no meaning anywhere. The description compensates for none of these — an agent cannot tell what 'picks' or 'window=all' means relative to the opened/scheduled scope it describes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description scopes the resource precisely: launches that have opened (live or closed) with real vote counts, explicitly excluding scheduled launches. It never states the action verb ('search'/'list') or that it accepts filters like date, sort and window, so an agent must infer from the name that this is a filtered list tool rather than, say, a single-launch lookup like get_gtm_launch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The exclusion 'Scheduled launches are not listed' implies a when-not condition, which is useful. However, no alternative sibling is named (e.g., get_gtm_launch for a single launch's details, or search_gtm_knowledge for other content), so the routing decision is left to 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