Samuelz® Marketing

Unternehmensprofil-Leistung lesen

get_business_profile_performance

Read-onlyIdempotent

Read daily organic Google Business Profile impressions, website/call clicks and direction requests for the exact connected location. Inclusive dates use the provider location calendar; exact timezone may be unknown. Missing days are not zero. Organic activity is not paid spend, ROAS or proven enquiries. No publishing/profile changes. POST /api/v1/tenant/read/get_business_profile_performance.

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": {
      "connectionId": "<connectionId>",
      "dateRange": "<dateRange>"
    },
    "name": "get_business_profile_performance"
  }
}

Input Schema

Name	Required	Description	Default
`dateRange`	Yes
`comparison`	No
`connectionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds genuinely useful data-quality behavior: provider location calendar for inclusive dates, possibly unknown timezone, and 'missing days are not zero' for gaps. It also confirms no publishing or profile changes occur, though it says nothing about pagination or rate limits.

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?

Front-loaded with the payload (what is read) followed by caveats, with no filler sentences. The style is telegraphic and the trailing endpoint path adds little for an agent, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a metric-reading tool with a nested date object, a comparison period, and no output schema, the description covers metrics and data-quality caveats but leaves open how the comparison period is returned and whether results are per-day or aggregated. Adequate but with visible gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it only partially does: it clarifies that the date range is inclusive on a provider-calendar basis and binds the call to one connected location, but the 'comparison' parameter is never mentioned and no format, alignment, or output-granularity guidance is given.

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?

States a specific verb (Read) plus a precisely scoped resource: daily organic Google Business Profile impressions, website/call clicks and direction requests. The 'organic' qualifier and the explicit 'not paid spend, ROAS' negation separate it from paid-performance siblings such as get_advertising_performance without needing to open a schema.

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?

Usage context is implied rather than stated: 'for the exact connected location' and 'Organic activity is not paid spend' tell the agent which question this answers, but there is no explicit when-to-use or when-not-to-use, and no named alternative for profile data versus search/website analytics.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Samuelz® Marketing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?