Skip to main content
Glama

List business profiles

list_business_profiles
Read-onlyIdempotent

List Google Business Profiles you can access, optionally limited to one workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
workspace_idNoLimit to this workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true, so safety and idempotency are covered. The description adds that results are limited to profiles 'you can access,' which is useful permission context, but it does not disclose pagination behavior or result completeness. With annotations carrying the safety profile, a 3 is appropriate.

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?

The description is a single sentence with no wasted words, and the core operation plus optional filter are front-loaded. It is appropriately sized for a simple list tool.

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 low-complexity list tool with full schema coverage and read-only annotations, the description is nearly complete. It covers access scope and the optional workspace filter. The only minor gap is absence of any note about result paging or whether all profiles are returned at once, which is not critical given the simple contract.

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 coverage is 100% and the single workspace_id parameter is already documented as 'Limit to this workspace.' The description reinforces that the limitation is optional, but adds no syntax or format details beyond the schema. Baseline 3 is correct when the schema fully documents the parameter.

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 states a specific verb and resource: list Google Business Profiles. It also adds the access scope 'you can access' and optional workspace filtering, making the operation clear. It does not explicitly distinguish itself from siblings like get_business_profile or list_workspaces, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for listing accessible profiles and notes the optional workspace limit, but it does not say when to prefer this tool over alternatives such as get_business_profile or list_workspaces. The guidance is adequate but not explicit.

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