Skip to main content
Glama
zhangluka

grain-seo-mcp

by zhangluka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bing_analytics_compare_periods

Compare Bing search performance metrics across two date ranges to identify trends and changes in traffic and rankings.

Instructions

Compare performance between two date ranges in Bing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteUrlYesThe URL of the site
startDate1YesStart date of period 1 (YYYY-MM-DD)
endDate1YesEnd date of period 1 (YYYY-MM-DD)
startDate2YesStart date of period 2 (YYYY-MM-DD)
endDate2YesEnd date of period 2 (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. The description does not disclose whether the tool is read-only, required permissions, or what 'performance' metrics are returned. Description carries full burden but fails.

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?

Single sentence, no fluff, front-loaded. However, it could be slightly more informative without increasing length significantly.

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

Completeness2/5

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

No output schema and no description of return value. With many sibling tools, more context needed to differentiate. Incomplete for practical use.

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%, so baseline is 3. Description adds minimal context by implying the date ranges are the periods to compare, but no additional meaning beyond schema.

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 the tool compares performance between two date ranges in Bing, which is specific and distinguishes from trend or query tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool over alternatives like bing_analytics_trends or bing_analytics_detect_anomalies. The many sibling tools increase the need for contextual usage hints.

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

Deploy Server

Other Tools