Skip to main content
Glama
Sign In
FeedDoctor MCP

FeedDoctor MCP

by anthonymorey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Feed & Account Health Summary

feed_health_summary
Read-onlyIdempotent

Combines Google and Microsoft Merchant Center account issues, feed upload status, product approval counts, and top disapproval causes into one normalized summary for quick feed diagnosis.

Instructions

Combines Google Merchant API v1 and Microsoft Merchant Center account issues, feed/dataSource upload status, product approval counts, and top disapproval causes into a single normalized summary.

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

Input Schema

NameRequiredDescriptionDefault
platformNoPlatform scope: "google", "microsoft", or "both".both
credentialsNoOptional per-call credential overrides. If omitted, credentials are resolved from the HTTP Authorization Bearer token / headers or self-host environment variables.
googleAccountIdNoGoogle Merchant Center account ID (defaults to primary resolved account).
microsoftMerchantIdNoMicrosoft Merchant Center store ID (defaults to primary resolved store).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

It informs the user that the tool synthesizes data from specific, known external sources (Google Merchant API v1 and Microsoft Merchant Center). This provides crucial behavioral context about the nature of the data aggregation, even with strong annotations.

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 definition is a single, dense sentence that provides maximum informational value with zero fluff or unnecessary phrasing.

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

Completeness4/5

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

Given the complexity of handling two major platform APIs and merging disparate data points, the description successfully defines the boundaries of the output summary. While it lacks an output schema, the description details exactly what metrics are included, providing sufficient guidance for the agent.

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 description adds context by naming the underlying technical standards and systems (Google Merchant API v1), which helps the agent understand the technical depth of the requested data beyond the simple parameter types in the 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 identifies a specific function (combining multiple data points) and a clear resource (health/account status) across two platforms, distinguishing it from singular list/diagnostics tools.

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?

The description clearly defines the scope (a comprehensive summary) but does not explicitly guide the user on when to prefer this broad view over a highly specific alternative like 'list_disapprovals.'

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