Skip to main content
Glama

GTM Daily

Search GTM jobs

search_jobs
Read-onlyIdempotent

Search open, published GTM Engineering jobs. Closed, expired, draft and unreviewed jobs never appear.

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

Input Schema

NameRequiredDescriptionDefault
toolNoNormalized tool name, e.g. Clay
limitNoMax results (default 10, max 50).
queryNo
cursorNoOpaque cursor from a previous result's next_cursor.
seniorityNo
arrangementNo
role_categoryNo
posted_within_daysNo

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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful scope: what is excluded (closed, expired, draft, unreviewed). It says nothing about pagination mechanics or result ordering beyond what the cursor schema field already conveys.

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 tight sentences with zero filler; the positive scope is front-loaded and the exclusion clause follows immediately.

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 and annotations cover safety, so return values and side effects need not be explained. However, a search tool with eight optional filters and 38% schema coverage leaves the agent guessing at what query, seniority, and role_category accept, which the description could have addressed.

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 description coverage is only 38%, and several parameters (query, seniority, role_category) are undocumented in both schema and description. The description supplies no parameter meaning at all, so it fails to compensate for the coverage gap.

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?

States a clear verb+resource ('Search ... GTM Engineering jobs') with a domain qualifier. It distinguishes itself from get_job_details by being a search rather than a detail fetch, though it does not name any sibling explicitly.

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

Usage Guidelines2/5

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

No guidance on when to use this versus get_job_details or get_gtm_job_market_data, both of which are plausibly overlapping candidates. The only usage-adjacent content is a data-visibility rule, not a selection rule.

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