Skip to main content
Glama

Connect Google Business Profile

connect_business_profile

Get a link the person opens to connect Google Business Profile to their Agency Autopilot account. One click, then their own Google sign-in. The link lasts 30 minutes and works once. It connects nothing by itself, and no password or token is ever entered in the conversation. Use when a tool reports the platform is not connected, or when asked to connect it.

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": "connect_business_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavior beyond annotations: the link expires in 30 minutes, works once, connects nothing by itself, and never requires a password or token in conversation. This is exactly the kind of operational context an agent needs for a non-destructive, open-world connection tool.

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 front-loaded with the returned artifact and then adds essential constraints and usage conditions. Every sentence earns its place, with no redundant or filler content.

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?

Although there is no output schema, the description explains what the caller gets back (a link), its lifetime, its single-use nature, and the credential-safety model. This is complete enough for an agent to call and explain the result.

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?

The tool has zero parameters, so there is no parameter semantics to explain. Baseline 4 is appropriate because the schema is empty and the description correctly does not invent parameter details.

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: get a link to connect Google Business Profile to the account. It clearly distinguishes this from sibling connection tools such as connect_google, connect_meta, and connect_wordpress.

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 explicit triggering conditions: use when a tool reports the platform is not connected or when asked to connect it. It does not explicitly contrast this with nearby alternatives like connect_google or link_account, but the platform-specific scope is clear.

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.