Skip to main content
Glama
chrischall

thumbtack-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

thumbtack_search_pros

Read-only

Search local service pros on Thumbtack by trade and US ZIP code. Compare up to 10 ranked professionals by rating, reviews, response time, and profile link—no account needed.

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

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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description goes beyond them by disclosing the result cap (up to 10 ranked pros), the ranked nature of results, the specific data fields returned, and that the call is anonymous with no account required. It omits rate limits and any note on what happens with an invalid ZIP or zero results.

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 short sentences, front-loaded with the action and scope, followed by return contents and the auth-free property. Every sentence carries distinct information and nothing is repeated from the schema.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the returned fields (rating, review count, lifetime hires, mean response time, profile URL) and the result cap, which the agent otherwise could not know. It is nearly complete; only error/empty-result behavior and any pagination caveat are unaddressed.

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 explains service, zip, limit, and the compact/full view enum in detail. The description only echoes the trade and ZIP-code dimensions and adds nothing about view or limit, so the baseline 3 applies.

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?

States a specific verb (Search) plus the resource (local service pros) and its two scoping dimensions (trade and US ZIP code). This clearly separates it from siblings like thumbtack_get_pro, thumbtack_get_pro_reviews, and thumbtack_resolve_service, which operate on a single already-identified pro or on name resolution.

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 the entry-point search use case, but never states when to use this versus thumbtack_resolve_service (which appears to be the canonicalisation step for loose trade names) or when to follow up with thumbtack_get_pro. No exclusions, prerequisites, or alternatives are given, so usage must be inferred from the sibling names.

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