Skip to main content
Glama

ADS Beast

seo_alerts_configure

Set alert thresholds for traffic, positions, backlinks, Core Web Vitals and AI visibility of a domain. AI: 1 AI request. May return a job_id (get_job_result).

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": {
      "domain": "<domain>"
    },
    "name": "seo_alerts_configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain without scheme.
client_idNo
key_keywordsNoKeywords to watch, comma-separated.
baseline_trafficNoCurrent monthly traffic.
notification_channelNoWhere alerts go.in_app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description goes beyond them by disclosing cost ('AI: 1 AI request') and asynchronous behavior ('May return a job_id (get_job_result)'), which are traits an agent cannot derive from annotations or schema.

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?

Three short sentences, front-loaded with the capability and tail-ended with cost and async notes. The 'AI: 1 AI request' fragment is terse to the point of being cryptic but is not wasteful.

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

Completeness3/5

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

For a configuration-writing tool with no output schema, the description leaves open whether existing alerts are replaced or merged, how thresholds are derived, and what a successful response contains beyond a possible job_id. Adequate to start the call, but not complete for a mutation of this type.

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 description coverage is 80%, so the baseline is 3. The description's list of watched metrics loosely contextualizes key_keywords and baseline_traffic, but it does not explain how a 'threshold' is expressed, which is notable since no threshold-valued parameter appears in the schema.

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?

States a specific verb ('Set alert thresholds') plus the resource and the exact metric families covered (traffic, positions, backlinks, Core Web Vitals, AI visibility). This is clearly distinct from siblings like list_alerts or seo_keywords_track, though it does not name any sibling explicitly.

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 is only implied by the verb 'Set' — the agent can infer this is the configuration entry point for alerts rather than reading them. The parenthetical '(get_job_result)' does provide concrete follow-up routing when a job_id is returned, but there is no when-not guidance or comparison to alternatives.

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.