mcp-erid

audit_ad_page

Audit an ad page for compliance: verify presence of 'Реклама' label, advertiser information, and erid link. Returns present, absent, or uncertain.

Instructions

Аудит рекламной поверхности: наличие пометки «Реклама», данных рекламодателя, привязки erid (present/absent/uncertain). Бесплатно.

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": {
      "url": "<url>"
    },
    "name": "audit_ad_page"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	URL рекламной страницы/поста для аудита маркировки.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description carries burden. It discloses what is checked (label, advertiser data, erid) and that it's free, but omits details on error handling, authentication needs, or rate limits.

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?

Two concise sentences that front-load the purpose and include a key trait (free). No unnecessary words.

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 tool's simplicity (one param, output schema exists), the description covers the core functionality. Lacks mention of prerequisites or error states, but sufficient for basic understanding.

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?

Schema coverage is 100% with a single parameter. Description adds context by specifying the URL is for an ad page/post, supplementing the schema's minLength constraint.

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 clearly states the tool audits an ad page, checking for specific elements: 'Реклама' label, advertiser data, erid presence. It distinguishes from sibling tools like audit_batch and verify_erid by focusing on a single page audit.

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?

Usage context is implied (audit a single ad page), but no explicit guidance on when to use this versus sibling tools (e.g., audit_batch for batch processing) or conditions like URL validity.

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

Deploy Server