Skip to main content
Glama

Honeyfield Marketing MCP

Bing Webmaster: Top pages

bing_top_pages
Read-only

Top-Seiten der Website in der Bing-Suche über den Zeitraum zusammengefasst: page, clicks, impressions, ctr_pct, avg_position, avg_click_position, sortiert nach Klicks. Gesamtzahlen der Website: bing_traffic. query: optional nur die Seiten, die für diese Suchanfrage erschienen. limit: max. Zeilen (Standard 50, höchstens 1000). days: die letzten N Tage bis heute (Standard 90); date_from/date_to ('YYYY-MM-DD', inklusiv) gehen vor, max. 365 Tage. Bing liefert die Suchdaten als WOCHENWERTE (eine Zeile je Woche, Feld date = Wochenstempel) — der Zeitraum greift auf ganze Wochen, kurze Zeiträume unter 7 Tagen sind oft leer. workspace: Slug des Kunden-Workspace (optional bei nur einem 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": "bing_top_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
queryNo
date_toNo
date_fromNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing the non-obvious weekly aggregation model (one row per week, date = week stamp), that the range snaps to whole weeks, that periods under 7 days are often empty, and the 365-day/1000-row ceilings. These are exactly the traits that cause wrong calls if unknown.

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-loads what the tool returns before the parameter notes, and each clause carries information. It is dense (one compressed paragraph) with no wasted sentences, though the field enumeration partially duplicates what the output schema already provides.

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?

An output schema exists, so return values are covered, and the description still adds the weekly-granularity caveat that shapes interpretation of results. For a read-only analytics call with zero required params, nothing an agent needs to invoke or read the result correctly is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description fully carries the burden and does: defaults and caps for limit (50/1000) and days (90/365), the inclusive 'YYYY-MM-DD' format and precedence for date_from/date_to, the filtering meaning of query, and the workspace slug behavior when only one workspace exists. All six parameters gain meaning beyond the bare schema types.

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?

Names a specific resource and scope ('Top-Seiten der Website in der Bing-Suche über den Zeitraum zusammengefasst') and enumerates the returned fields (clicks, impressions, ctr_pct, avg_position), plus the sort order. It explicitly contrasts itself with bing_traffic for site-wide totals, so an agent can separate it from that sibling without opening 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 Guidelines4/5

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

Gives explicit routing to bing_traffic for site totals and explains when the query parameter narrows results ('nur die Seiten, die für diese Suchanfrage erschienen'). It also documents the precedence of date_from/date_to over days. No exclusion against bing_top_queries or a statement of when page-level data is the wrong choice, so it stops short of a full 5.

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