Skip to main content
Glama

Client: ads, website and Analytics side by side, per page and search

whole_picture
Read-onlyIdempotent

The whole picture for one client: each page with its Google Ads numbers (paid clicks, cost, conversions), its Analytics numbers (visits from every source, engagement, leads) and its Search Console numbers (organic clicks, rank) side by side; the paid search terms against where the site already ranks for them; and what only the join shows (a page that gets paid clicks but never converts, paying for searches the site already wins free, a converting search worth an SEO page). Look at this before adjusting anything. Read-only.

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": {
      "client": "<client>"
    },
    "name": "whole_picture"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYesClient name from list_clients

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered; the closing 'Read-only' merely restates it. The description adds real behavioral value by describing what the return contains (concrete joined signals like 'a page that gets paid clicks but never converts'), which no annotation or output schema provides.

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?

One dense but front-loaded sentence that leads with the core deliverable and builds outward to examples. Every clause contributes, though the layered parentheticals make it heavier than strictly necessary.

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?

With no output schema, the description carries the full burden of explaining returns, and it does so thoroughly across all three data sources plus the derived insights. For a read-only cross-platform join tool, an agent has everything needed to call it correctly and interpret the result.

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 a single parameter with 100% schema description coverage, and the schema already states 'Client name from list_clients.' The description adds no additional meaning about the client parameter, so the baseline 3 for high-coverage schemas applies.

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 names a specific verb (join/aggregate) and resource (one client's Ads + Analytics + Search Console data per page and search term), and articulates the distinct value: 'what only the join shows.' This differentiates it from single-source siblings like ads_report, ga4_report, and gsc_query without opening their schemas.

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?

Explicit guidance: 'Look at this before adjusting anything,' which frames it as a pre-optimization diagnostic. However, it does not name the alternative reports (ads_report, client_overview, audit_client) or the condition that would select them, so the when-not side is inferred rather than stated.

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.