Skip to main content
Glama
chrischall

thumbtack-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

thumbtack_search_pros

Read-only

Search local service professionals by trade and ZIP code, receiving up to 10 ranked pros with ratings, reviews, and response times.

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.
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; "full" returns Thumbtack's whole records.
limitNoCap the number of pros returned (upstream page size is 10).
serviceYesTrade or service, e.g. "house cleaning", "plumbing", "electrician". Loose names are canonicalised by Thumbtack.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv0.1.2
    • removedInput schema / properties / compact
      Removed value: -{
-  "default": false,
-  "description": "Set 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.",
-  "type": "boolean"
-}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; \"full\" returns Thumbtack's whole records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description adds valuable context beyond that: it notes the operation is anonymous (no account needed) and specifies the return fields (rating, review count, lifetime hires, mean response time, profile URL). This goes beyond the annotation's safety profile 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 sentences, zero fluff, and the primary purpose is front-loaded. The anonymity note is a useful extra that doesn't dilute the message. Every sentence earns its place.

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?

For a read-only search tool with four well-documented parameters and no output schema, the description is complete: it states the return fields, the result limit (up to 10), and the anonymous access model. Nothing essential for correct invocation is missing.

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 schema already documents all four parameters clearly. The description reiterates the service and ZIP purpose but adds no new parameter-specific details beyond what the schema provides, which is the baseline for full coverage.

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 states a specific verb (Search), a resource (local service pros), and the scope (by trade and US ZIP code). It clearly distinguishes this from sibling tools like thumbtack_get_pro (single pro) or thumbtack_get_pro_reviews (reviews), making the purpose unambiguous.

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 description implies when to use it (searching for pros by trade and ZIP), but it does not explicitly name alternatives or provide 'when-not-to-use' guidance. The context is clear, but no exclusions or sibling references are given, leaving usage to inference.

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

Deploy Server

Other Tools