Skip to main content
Glama

seo_get_settings

Retrieve cvrt-seo-manager settings organized by section for a site, returning secret values only as set flags instead of raw data.

Instructions

Get cvrt-seo-manager settings grouped by section (titles, robots, social, knowledge_graph, schema, verification, indexnow, search_console, advanced, sitemap, breadcrumbs, images, links, local_seo, monitor_404, woocommerce). Secret values are returned as { set: boolean }, never raw.

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": {
      "site": "<site>"
    },
    "name": "seo_get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose two real behaviors: results are grouped by section, and secret values are masked as { set: boolean } rather than returned raw. It does not state whether the call is strictly read-only, what permissions are needed, or how large the grouped payload typically is.

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?

Two tightly written sentences with the core behavior front-loaded. The long parenthetical section list is heavy but serves a purpose by telling the agent what groupings to expect in the response.

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 one-parameter read tool with no output schema and no annotations, the definition covers the essentials: scope, section grouping, and secret redaction. It is slightly thin on the shape of the returned section objects, but nothing critical to calling it is missing.

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 100% and the single `site` parameter is documented in-schema with a pointer to list_sites. The description adds no meaning about the parameter, so the baseline 3 applies.

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 ("Get cvrt-seo-manager settings") plus the organizing principle (grouped by section) and enumerates the sections. The read verb implicitly separates it from seo_update_settings/seo_import_settings, but it never names those siblings or explicitly contrasts with seo_export_settings.

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?

There is no when-to-use or when-not guidance. Given siblings like seo_export_settings and seo_import_settings that plausibly also surface settings, the agent is left to infer that this is the plain read path rather than an export/backup path.

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