Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_network_sync_manifest

Fetch opt-in network catalog changes since an ISO timestamp to keep ad network data synchronized.

Instructions

Pull opt-in network catalog changes since an ISO timestamp.

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

Input Schema

NameRequiredDescriptionDefault
sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses only that the pull is opt-in and incremental from a timestamp, while omitting whether the operation is read-only, what permissions or auth are required, whether changes are destructive, whether results are paginated, and what the return shape is.

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 front-loaded sentence with no wasted words. It is appropriately concise, even though the underlying specification is incomplete in other dimensions.

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?

For a network sync tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It should explain what the manifest returns, whether sync is incremental and idempotent, and what an agent should do with the result before invoking it.

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?

The schema has 0% description coverage for the single parameter "since," but the description does add useful semantics by specifying an ISO timestamp format. It does not clarify that the parameter is optional, what the default behavior is when omitted, or how timezone is handled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: pulling opt-in network catalog changes, with an incremental timestamp scope. However, the terms "manifest" and "opt-in network catalog" remain somewhat opaque, and the description does not differentiate this tool from nearby network catalog or sync siblings such as ads_network_inventory_list or ads_network_platform_report.

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?

The description implies incremental synchronization by using "since an ISO timestamp," but gives no explicit guidance on when to use this tool versus alternatives like ads_network_platform_list, ads_network_inventory_list, or ads_network_status. There are no exclusions, prerequisites, or named alternatives.

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