Skip to main content
Glama
chrischall

thumbtack-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

thumbtack_get_pro

Read-only

Retrieve a Thumbtack pro's profile from a URL to view their rating, credentials, location, and service offerings.

Instructions

Read a Thumbtack pro's profile: name, description, location, aggregate rating, plus credentials (background check, licences) and the section inventory. Takes a profile URL from thumbtack_search_pros.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull https://www.thumbtack.com/... pro profile URL.
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.

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. Changed1 schema field changedv0.1.2
    • 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.2/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes this is a safe read operation, and the description reinforces that with 'Read'. It adds useful behavioral context by detailing exactly what profile data is returned, including credentials and section inventory, which goes beyond the annotation's bare safety signal.

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?

The description is two sentences with no filler. The first sentence names the action and return fields, and the second sentence ties the tool into the search workflow, so every sentence earns its place.

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?

For a read-only profile fetch with one required and one optional parameter, the description is largely complete: it lists the output fields and the required input source. It does not explain 'section inventory' in detail or describe likely errors, but the schema covers the parameter behavior and no output schema is expected.

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 coverage is 100%, so the schema fully documents the url and view parameters, including the compact/full distinction. The description adds one meaningful connection by stating the URL comes from thumbtack_search_pros, but it does not add detail about the view parameter; baseline 3 is appropriate.

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 action ('Read a Thumbtack pro's profile') and a clear resource, then enumerates the returned content: name, description, location, aggregate rating, credentials, and section inventory. It also distinguishes this tool from review- or search-related siblings by framing it as the profile reader fed by thumbtack_search_pros.

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 provides clear usage context by saying it takes a profile URL from thumbtack_search_pros, which tells an agent when in the workflow to call this tool. It does not explicitly list exclusions or name alternatives like thumbtack_get_pro_reviews, but the input source and profile focus imply the right selection.

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