Skip to main content
Glama

seo_import_settings

Imports SEO settings from a flat csm_* key-value map, writes only non-secret options, and returns how many settings were saved.

Instructions

Import settings from a flat { csm_name: value } map (the seo_export_settings shape). Only csm_* keys are written; secrets (csm_indexnow_key, csm_gsc_service_account, csm_github_token) are never imported. Returns the number of options written.

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>",
      "data": "<data>"
    },
    "name": "seo_import_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesFlat map of csm_* option names to values, e.g. { csm_title_separator: '|' }
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.14.0
    • changedInput schema / properties / data / description
      Previous value: -"Settings payload to import"New value: +"Flat map of csm_* option names to values, e.g. { csm_title_separator: '|' }"
  2. Addedv3.4.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present the description carries the full burden, and it does disclose real behavior: only csm_* keys are written, three named secret keys are never imported, and the return value is a count of options written. It stays silent on the operationally important question of whether existing settings are merged or overwritten, and on any capability/permission requirements.

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?

Three short sentences, each front-loaded with its most important fact: format, filtering rule with concrete key names, then return value. No filler and nothing repeated.

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 two-parameter write tool with no annotations and no output schema, the definition covers input shape, exclusions, and return value, which is most of what an agent needs. The remaining gap is merge-vs-replace semantics on existing options, which materially affects whether calling it is safe.

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% and both parameters are described in the schema itself, so the baseline is 3. The description adds genuine meaning on top by defining what belongs in the `data` map (csm_* keys matching the export shape) and confirming that secret keys in that map will be silently dropped rather than written.

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?

Names a specific verb and resource (import settings) and pins the input format to a flat { csm_name: value } map, explicitly tying it to the seo_export_settings shape. That format statement is enough to separate it from the other import siblings (csv, migrate, redirects).

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?

The parenthetical reference to the seo_export_settings shape effectively tells the agent this is the round-trip counterpart of export, and the secret list defines a clear 'these keys are ignored' boundary. It does not, however, state when to prefer this over seo_import_migrate or seo_update_settings for individual edits.

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