Unstuck

Find Local Businesses

business_listings

Read-onlyIdempotent

Find local businesses of a kind in a city, as listed on Google Maps: name, address, phone number, website, star rating and number of reviews. Use it to build a lead list, find competitors, or look up a business's contact details. Price: $0.03 per successful call; failed calls are free.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	How many businesses, default 10, max 20.
`query`	Yes	Type of business or name, e.g. "plumbers" or "taco truck".
`api_key`	No	Your Unstuck API key, if this connection has none. Leave empty to try free tools or to get a key and payment link.
`location`	No	City and state, e.g. "Houston, TX". Required unless the connection sets a default location.

Output Schema

TableJSON Schema

Name	Required	Description
`query`	Yes
`results`	Yes
`location`	Yes	Location searched.
`balance_usd`	Yes	Remaining prepaid balance, USD.
`charged_usd`	Yes	Amount charged for this call, USD.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

addedInput schema / properties / api_key

Added value: +{
+  "description": "Your Unstuck API key, if this connection has none. Leave empty to try free tools or to get a key and payment link.",
+  "maxLength": 200,
+  "type": "string"
+}

First observedOct 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real non-annotated context: per-call cost ($0.03 per successful call, failed calls free) and the exact field set returned. It omits rate limits and the free-tier/API-key behavior, which the schema partially covers.

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 tight sentences with zero filler: what it returns first, then when to use it, then cost. Pricing is placed last where it belongs, and nothing is repeated from the schema or annotations.

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?

An output schema exists, so return values need not be explained, and the description still previews them usefully. Coverage of purpose, use cases and cost is complete for a small read-only lookup tool. The one missing piece is sibling routing to business_reviews for review-level detail.

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 query, location, limit and api_key are each fully documented in the schema with examples. The description only echoes 'of a kind in a city', adding no format, default-count, or validation nuance beyond what the schema provides. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find local businesses'), the scope ('in a city'), the data source ('as listed on Google Maps'), and enumerates the returned fields. It is unmistakable what the tool does. It does not distinguish itself from the sibling business_reviews, which touches the same star-rating/review data, so it falls short of a 5.

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?

Gives concrete usage contexts ('build a lead list, find competitors, or look up a business's contact details'), which is clearer than mere implied usage. However, it names no alternatives or exclusions — e.g. routing the agent to business_reviews when it needs review text rather than a listing.

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

All Unstuck tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?