Skip to main content
Glama

Connect many listings

connect_locations
Idempotent

Connects many listings at once from their public links (Google Maps by default: one link per office or shop), up to 100 per call (send more in several calls). Each row may carry the office name and a reference (the customer’s own id, to match and filter later). Google Maps needs owner_attestation true: only send it if the user confirmed they own or manage these businesses or are authorized by their owner. Returns one result per row (connected, already_connected or error with the reason). If the batch is bigger than the plan allows, nothing is connected and the error says how many fit and how to make room; partial true connects the ones that fit. dry_run true checks everything without connecting. Needs a full API key: a key from the MCP sign-in (OAuth) can’t connect locations, so answer insufficient_scope by asking the user to add them in the dashboard (Connections → Add many locations) or to use an API key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locations": "<locations>"
    },
    "name": "connect_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoCheck every row and the plan limit without connecting anything.
partialNoConnect the rows that fit in the plan and report the rest. Default false: all or nothing.
platformNoA platform connected with a listing link. Default google_maps.
locationsYes
owner_attestationNoGoogle Maps: the user confirmed they own or manage these businesses, or are authorized by their owner.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the description's job is to add mutation-specific context. It exceeds that bar by describing per-row outcomes, all-or-nothing plan-limit behavior versus partial=true, dry_run no-op behavior, and the full API key/insufficient_scope requirement. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded and information-dense, with the purpose, batch limits, and auth constraint early. It is a long run-on paragraph with some repetition of schema details such as the 100-row cap and owner_attestation description, so it is slightly less concise than ideal.

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 must explain return behavior; it does so by naming one result per row (connected, already_connected, error) and the plan-limit error shape. It also covers auth, dry_run, partial, and Google Maps attestation, leaving no major operational gap for this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is 3; most parameter descriptions are already present. The description adds meaningful row-level semantics: one link per office/shop, optional name and reference, reference used to match/filter later, and the batch limit. It largely repeats the schema's owner_attestation and dry_run semantics, so it is not a full 5.

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?

Starts with a specific verb and resource: "Connects many listings at once from their public links." It scopes the operation to batches (up to 100) and identifies the Google Maps default, which distinguishes it from a single-link connect operation.

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 clear operational context: use it for batches, split larger batches into several calls, set dry_run for checks, partial for over-limit batches, and owner_attestation only after user confirmation. It does not explicitly name a sibling for single-listing connections, so the alternative routing is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources