Skip to main content
Glama

ADS Beast

seo_publish_safety

Read-only

Ask this before publishing or scheduling any article for a site. Returns its gradual-launch state: articles allowed today and already published, whether publishing is paused and why, and indexed versus kept-out articles. Rules: 2 new articles a day at start, plus 1 a week up to 6; one language version of a topic a day; search visits below 30% of the weekly median pause publishing until a person lifts it; articles under 600 words, without a meta description or reusing another language's address get noindex and stay out of the sitemap. Do not plan around these limits: mass near-identical pages is how sites lose Google traffic overnight.

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

Input Schema

NameRequiredDescriptionDefault
client_idNoThe site's client id; omit for the organization overview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only and non-destructive annotations, the description discloses substantial behavior: the numeric launch limits, language-version rules, pause triggers, noindex conditions, and a warning not to plan around those limits. This adds real decision-making context rather than repeating annotation metadata.

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 description is front-loaded with the trigger and return summary, then states the operating rules. Despite the detail, every sentence supports correct use or interpretation, and there is no redundant restatement of the name or annotations.

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?

For a read-only check with one optional, fully documented parameter and no output schema, the definition supplies enough return-state context and policy detail for an agent to call it correctly and interpret the result. The remaining gaps are minor and not necessary for invocation.

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%, and the schema already explains that client_id is the site's client id and may be omitted for an organization overview. The description only implies site context ('for a site') and adds no new parameter meaning, so the baseline 3 is appropriate.

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 gives a specific action and resource: it is a pre-publish safety check that returns a site's gradual-launch state, including allowed/published articles, pause status, and index status. It clearly distinguishes itself from sibling article-generation and ad-publish tools by focusing on article publishing safety for a site.

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?

It explicitly says to ask this before publishing or scheduling any article for a site, which gives strong when-to-use guidance. It does not name alternative tools or spell out when-not-to-use cases, so it falls 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.