Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Apply Fix Tool

adataforseo.apply_fix

Applies a selected fix for one SEO audit finding by updating sSeo fields or adding a redirect; preview changes first, then record and undo as needed.

Instructions

Changes the site. Applies the fix of one finding (sSeo fields or a redirect), with the same permission checks as the manager page; every change is recorded and can be undone with adataforseo.undo_change. Set preview to true to see the changes first.

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": {
      "issue": "<issue>"
    },
    "name": "adataforseo.apply_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueYesIssue id from adataforseo.audit
fieldsNoOverride suggested sSeo values: meta_title, meta_description, meta_keywords, robots, canonical_url, exclude_from_sitemap
new_urlNoRedirect target, when the fix is a redirect
previewNoOnly show the changes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description usefully adds that permission checks mirror the manager page, that every change is recorded, and that it is undoable. It still omits failure behavior and whether omitted fields are left untouched, so the disclosure is helpful but not complete.

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 core action and followed by safety-relevant details. "Changes the site" is slightly vague but quickly qualified, and no sentence is wasted.

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?

For a mutation tool with no output schema and a nested fields object, the description covers permissions, auditability, undo, and preview. Remaining gaps around error handling and field-merge semantics are minor given the fully documented schema.

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%, so the schema already documents all four parameters including the nested fields object. The description adds only marginal meaning, clarifying that new_url applies when the fix is a redirect and that preview shows changes without applying them.

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 and resource ("Applies the fix of one finding") and scopes it to sSeo fields or a redirect, which distinguishes it from read-only siblings like adataforseo.audit. It does not explicitly contrast with adataforseo.create_draft, but the mutation scope is clear.

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?

Gives useful context: use preview=true to inspect changes first, and changes can be reverted with adataforseo.undo_change. However, it never states when to prefer this over alternatives such as create_draft, nor any preconditions beyond the issue id coming from audit.

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