Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

Configure domain DNS

configure_domain_dns
Destructive

Requires the account session, current X-Organization-Id and CSRF for writes. Set up to three known DKIM selectors and choose whether IP rotation is expected. Expected rotation keeps history without notices; alias changes still notify. Does not discover selectors, enable monitoring or authenticate sent messages. Send manual_expires_on, dns, or both. Omitted settings are preserved. DNS requires both selectors and rotating_addresses. A manual date does not change registry data or confirm renewal payment. An identical retry is idempotent. A conflicting revision returns 409.

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": {
      "id": "<id>",
      "revision": "<revision>",
      "dns": "<dns>"
    },
    "name": "configure_domain_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOwned tab ID from list_tabs.
dnsYesKnown selectors and expected IP rotation. Selector discovery is not performed.
revisionYesCurrent revision from the corresponding settings or monitor. Use zero for the first change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / dns / properties / dkim_selectors / description
      Added value: +"Up to three known DKIM selectors. This does not discover selectors or authenticate messages."
    • addedInput schema / properties / dns / properties / rotating_addresses / description
      Added value: +"True when IP rotation is expected. Preserve history without rotation notices; alias changes still notify."
  2. Added
  3. Removed
  4. Added

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false) the description discloses the auth contract (session, current X-Organization-Id, CSRF for writes), that omitted settings are preserved, that non-rotation suppresses notices while alias changes still notify, and that a conflicting revision returns 409. The retry/idempotency sentence is consistent with the annotation only if read as same-revision retries versus revision-bumping writes, but it is phrased loosely enough to be ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The auth prerequisite is front-loaded and the content is dense, but the body is a run of telegraphic fragments with no grouping between prerequisites, semantics, and error behavior. Some material (selector discovery is not performed) is repeated both here and in the schema descriptions.

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 destructive write with a nested object and no output schema, the description covers the important unknowns: credentials needed, preservation of omitted settings, notification side effects, and the 409 conflict path. The only real gap is the inaccurate parameter instruction, which undermines otherwise solid completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 id, revision and the nested dns object. The description adds 'DNS requires both selectors and rotating_addresses', which merely restates the schema's required list, and worse, instructs 'Send manual_expires_on, dns, or both' — manual_expires_on does not exist in the input schema and dns is required, so this sentence actively misleads about the parameter set.

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?

The description gives a concrete verb and resource: setting DKIM selectors (up to three) and declaring whether IP rotation is expected for a domain. The closing exclusion 'Does not ... enable monitoring' implicitly separates it from configure_domain_monitor, though it does not name that sibling outright.

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?

Some usage direction is present ('Send manual_expires_on, dns, or both', plus explicit non-goals: no selector discovery, no monitoring, no message authentication). There is no explicit statement of when to prefer this over configure_domain_monitor or set_domain_expiry, so the routing guidance is only implied.

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

All pageaudit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources