Skip to main content
Glama

Business Profile: the listing's categories, description, service areas and services

gbp_profile
Read-onlyIdempotent

The editable fields of one Business Profile listing: main and additional categories (with ids), description, service areas (with place ids), services, website and phone. Shows what Google shows now; a field whose edit Google is still reviewing appears under pending_review with both values. Read it before gbp_update_profile, and again after an edit to see whether Google has published it.

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": {
      "gbp_location_id": "<gbp_location_id>"
    },
    "name": "gbp_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
gbp_location_idYesFrom gbp_list_locations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one non-obvious behavioral trait beyond that: a field still under Google review appears under pending_review with both values, which tells the agent to expect an unusual payload shape. That is real added context, but it is a single detail and versioning/rate behavior is not addressed, so a 4 is a stretch and a 3 undersells it; on balance 4 is not warranted given the sparse behavioral disclosure.

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?

Two sentences, front-loaded with the field inventory and followed by the pending_review caveat and the read/verify workflow. Every clause carries information; nothing is padded.

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 single-parameter read tool with no output schema, the description covers the important unknowns: which fields come back, that values reflect current Google state, and how in-review edits are surfaced. It does not describe whether absent fields are omitted or null, a minor residual gap for a payload-shaped tool.

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?

There is only one parameter, gbp_location_id, and schema description coverage is 100% with the schema itself stating 'From gbp_list_locations.' The description adds no meaning about the identifier beyond that, so the high-coverage baseline of 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?

The description enumerates the exact resource and its fields ('main and additional categories (with ids), description, service areas (with place ids), services, website and phone') and makes clear this is a read of one listing through 'Shows what Google shows now.' It is clearly not a mutation tool, distinguishing it from gbp_update_profile, though the framing is a noun phrase rather than an explicit verb+resource statement.

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?

Workflow guidance is explicit: 'Read it before gbp_update_profile, and again after an edit to see whether Google has published it,' naming the sibling and the condition that selects it. No when-not-to-use case is stated, which keeps it short of a 5, but the sequencing advice is genuinely actionable.

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.