Skip to main content
Glama

Visibility Genies

Get business posts

get_business_updates

Collects the posts, offers and events a business published on its Google Business Profile, newest first. Name the business with exactly one of businessName, cid or placeId. Usually completes within this call; if the queued job is still running you get status 'processing' plus a taskId, so call again with that taskId in 30-60 seconds to collect it at no extra cost. Estimated price: $0.01 for 10 posts, at twice the Local page's normal-priority rate; posts bought within a day, here or on the Local page, are answered at no charge. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_business_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidNoGoogle-defined business CID (from get_local_serp_results rows). Most precise identifier.
nearNoCoordinate to search from. Use it when the business name is ambiguous; otherwise locationCode is enough.
depthNoNumber of posts to collect (10-100). Defaults to 10. Billed per 10 posts.
taskIdNoResume a previous call that returned status "processing". Pass back the bare taskId exactly as returned. Resuming charges no extra credits.
placeIdNoGoogle Maps place_id (from get_local_serp_results rows).
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
businessNameNoBusiness name as it appears on Google. Supply exactly one of businessName, cid, or placeId.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
locationCodeNoLocation code. Ignored when `near` is set; otherwise defaults to the project's market.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
statusYes
taskIdYes
updatesNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the asynchronous processing model, the no-extra-cost resume path, per-call pricing, the workspace spend limit, the fact that a call can be refused before purchase, and the approvedMaxCostUsd recovery flow. This is unusually complete behavioral context for an agent.

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?

The description is front-loaded with purpose, then identifiers, async handling, and billing. It is somewhat long and the pricing/spend-limit sentences are dense, but nearly all information is relevant to correct invocation.

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?

Given the 10 parameters, nested objects, rich schema descriptions, output schema, and annotations, the description covers the remaining decision-critical behavior: async resumption, cost approval, and identifier selection. Nothing essential appears to be missing.

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 100%, so the baseline is 3. The description adds important meaning beyond the schema: exactly one identifier must be supplied, taskId resumes a prior call without extra charge, and approvedMaxCostUsd is only used after a refusal and only with user approval.

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 verb and resource: collects posts, offers and events published on a Google Business Profile, newest first. That is enough to distinguish it from sibling tools such as get_business_profile and get_business_reviews.

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?

It gives clear usage conditions: supply exactly one of businessName, cid or placeId, and resume a 'processing' job with taskId after 30-60 seconds. It does not explicitly compare the tool with sibling tools or say when not to use it, so it falls short of a 5.

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