Skip to main content
Glama

pirch

by com.pirchjobs

search_verified_jobs

Search pirch's pool of verified-live job listings. Every job returned was opened and confirmed real and accepting applicants by pirch within the last 72 hours — dead and ghost listings are removed automatically, so results can be trusted as live right now. Free, public data. When showing a job to a user, link its url (the pirch page, which shows the verification and links to the original posting).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoOccupation slug filter (e.g. 'ux-designer', 'registered-nurse'). Use get_jobs_overview to see which slugs currently have jobs.
limitNoMax results, 1-25 (default 10).
queryNoFree-text search over title, company, location, occupation and summary (e.g. 'senior product designer').
locationNoSubstring match on the listing's location (e.g. 'Denver'). Note: remote jobs often have no city and won't match a city filter — filter workmode=remote instead.
workmodeNoFilter by work mode.

TDQS

A4.8/5.0
Behavior5/5

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

No annotations provided, so description bears full burden. It discloses that jobs are verified within 72 hours, dead listings removed, and data is free/public. No contradictions.

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?

Three sentences, front-loaded with purpose, then verification detail, then usage tip. No filler.

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?

Tool has 5 params, no output schema, 2 siblings. Description covers input filters, verification, linking guidance, and references sibling for role slugs. Complete for complexity.

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

Parameters5/5

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

Schema coverage is 100% with descriptions. Description adds value: notes role uses slugs from get_jobs_overview, and location param explains remote jobs may not match city filters.

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 it searches pirch's verified-live job listings, specifying that jobs are confirmed real and accepting applicants. It distinguishes from siblings: get_jobs_overview (overview) and get_verified_job (single job).

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?

The description explains when to use the tool (search verified jobs) and gives a usage tip (link to url). It does not explicitly state when not to use it, but the purpose is contextually clear.

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

All pirch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool serves a distinct purpose: get_jobs_overview provides summary counts, search_verified_jobs returns filtered lists, and get_verified_job retrieves full details by ID. There is no functional overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (get_, search_), making them predictable and easy to understand.

Tool Count4/5

With only 3 tools, the server is minimally scoped but covers the essential operations for verified job data access. The count is appropriate for a focused read-only service.

Completeness5/5

The tool set covers the full read lifecycle: overview, search, and detail retrieval. No write operations are needed for this domain, so there are no obvious gaps.

Resources