Skip to main content
Glama
chrischall

thumbtack-mcp

by chrischall

thumbtack_search_pros

Read-only

Search Thumbtack for local service professionals by trade and ZIP code. Get up to 10 ranked pros with ratings, reviews, and response times—no account required.

Instructions

Search Thumbtack for local service pros by trade and US ZIP code. Returns up to 10 ranked pros with rating, review count, lifetime hires, mean response time and profile URL. Anonymous — no account needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipYes5-digit US ZIP code to search near.
limitNoCap the number of pros returned (upstream page size is 10).
compactNoSet true for slim summaries (name, rating, reviews, hires, response time, url). Default false returns the full upstream records, which are large and mostly tracking metadata.
serviceYesTrade or service, e.g. "house cleaning", "plumbing", "electrician". Loose names are canonicalised by Thumbtack.
Behavior4/5

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

The readOnlyHint annotation already marks it safe, and the description adds valuable context: 'Anonymous — no account needed' and 'Returns up to 10 ranked pros' with specific fields. This goes beyond the annotation without contradicting it.

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 crisp sentences: the first states the action and inputs, the second states the output shape and authentication note. No filler or redundant information.

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?

No output schema exists, so the description compensates by explicitly listing return fields (rating, review count, lifetime hires, mean response time, profile URL) and the cap of 10. Combined with detailed parameter schemas and the readOnly annotation, this is sufficient for correct selection and invocation.

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 description coverage is 100%, so the structured data already explains all four parameters. The description only loosely maps 'trade' to service and 'ZIP' to zip, adding no extra parameter-level meaning beyond the schema.

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 opens with 'Search Thumbtack for local service pros by trade and US ZIP code' – a specific verb, resource, and query criteria. It clearly distinguishes from sibling tools like thumbtack_get_pro (single pro) and thumbtack_get_pro_reviews (reviews) by describing search behavior and result fields.

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?

Clear usage context: search by trade and ZIP, returns ranked pros, and 'Anonymous — no account needed' implies it works without authentication. However, it does not explicitly name alternative tools or state when not to use it, stopping short of full guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/thumbtack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server