Keytomic

Delete author profile

delete_author_profile

Destructive

Deletes an author profile from a site, the same as in Keytomic. When it was the default, the newest other author becomes the default; when no author remains, authors turn off. When Article Settings named it, that setting is cleared. The result says which of these happened. Ask the user before calling it. Spends no credits.

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": {
      "projectId": "<projectId>",
      "authorProfileId": "<authorProfileId>"
    },
    "name": "delete_author_profile"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	Yes	Site to act on, from list_sites.
`authorProfileId`	Yes	Author profile to act on, from the settings section of get_project.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes well beyond them by spelling out the cascade: the newest remaining author becomes default, authors are turned off when none remain, and any Article Settings reference is cleared. It also states that the response reports which of those cases occurred, and that the call costs no credits — genuinely non-obvious behavior an agent could not infer.

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?

Front-loaded with the action, then the cascade consequences, then the confirmation requirement — a sensible ordering with no padding. The clause 'the same as in Keytomic' is an opaque product reference that adds little for an agent and is the only soft spot.

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 destructive tool with no output schema, it covers the important gaps: downstream effects, confirmation requirement, and cost. It does not explicitly say the deletion is irreversible or whether permissions beyond site access are needed, but the essentials for correct invocation are present.

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% and both parameters carry their own descriptions including where to source the IDs (list_sites, get_project), so the schema does the work. The description adds no additional parameter meaning, which matches the baseline of 3 under full coverage.

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?

States a specific verb and resource ('Deletes an author profile from a site') and immediately scopes the side effects, which cleanly separates it from save_author_profile and update_brand_profile in the sibling list without needing to name them.

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?

Gives an explicit precondition — 'Ask the user before calling it' — which is exactly the right guidance for a destructive operation, and notes it spends no credits. It stops short of naming an alternative action (e.g. what to do if the goal is only to change the default author), so it is not a full when/when-not statement.

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

All Keytomic tools Inspect

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

Need Help?