MCPHerramientas MCP/Ubicaciones/list_locations

list_locations

Readlocations:read

List a client's business locations with name, address, category, tags, status, verification, pending changes, and publisher connections. Starting point for any location-specific work. Each row has a `kind`: 'location' is a physical business; 'website' is a brand's website (e.g. synup.com) tracked for reviews, SEO, AEO and social only — it has no address, category, listings or Google Business Profile, so never publish, verify or edit listing fields on it, and call it a website, not a location.

Parámetros

clientIdstringopcional

Limit to a single client's locations (get the id from list_clients). Omit to list across all of the agency's locations. Accepts the database ID or public cli- ID. IDs must belong to the authenticated agency and permitted client.

searchstringopcional

Free-text search over the location's name, street address, city, or phone (case-insensitive, partial matches allowed).

A single status bucket. Allowed values: "all", "active" (not archived), "archived", "archival_pending", "verification_pending" (approval pending), "unapproved", "requires_action". Defaults to all.

tagsstring[]opcional

Internal tags — matches a location that has any of these.

categoriesstring[]opcional

Category names — matches a location whose general or Google category is any of these.

verification("verified" | "pending" | "unverified" | "unknown")[]opcional

Google verification state. Allowed values: "verified", "pending", "unverified", "unknown".

createdAfterstringopcional

Only locations created on or after this date (e.g. "2026-01-01").

createdBeforestringopcional

Only locations created on or before this date.

cursorstringopcional

Leave empty for the first page; to get the next page, pass the `nextCursor` from the previous response.

limitnumberopcional

How many locations to return per page (1–200, default 50).

Solicitud de ejemplo

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_locations",
    "arguments": {}
  }
}

Respuesta de ejemplo

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "..."
      }
    ]
  }
}

La forma de la respuesta se muestra a modo ilustrativo — el contenido real depende de la herramienta y de tus datos.