Mark

Delete Source

delete_source

Destructive

Deletes a pasted note (a source with type note) from the Claims & sources page. It also leaves the source picker. Cannot be undone. Refused while any claim quotes the note, active or retired (list_claims shows claims per source), or while brand profile evidence cites it (update_brand_profile). Other source types cannot be deleted here. Related: list_claims, update_source.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	The note's id from list_claims.

Output Schema

Name	Required	Description	Default
`appUrl`	Yes
`deletedId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing irreversibility ('Cannot be undone'), a side effect the annotations do not capture ('leaves the source picker'), and two server-side refusal preconditions with the tools that verify them. This is exactly the extra context destructiveHint alone cannot supply.

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 verb and object, followed by refusals and a Related line. Dense but every sentence carries information; the trailing 'Related:' list is the only mildly extraneous element.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and the description covers the preconditions, irreversibility, and side effects an agent needs before invoking a destructive single-parameter tool. Nothing material 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 sole parameter's description already says 'The note's id from list_claims', which the tool description merely echoes. No new syntax, format, or sourcing detail is added, so baseline 3 applies.

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 (deletes) and a narrowly-scoped resource (a pasted note, i.e. a source with type note), and explicitly excludes other source types. This distinguishes it from siblings like delete_post, delete_assets, and delete_site without opening a schema.

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 concrete when-not conditions: refusal while any claim quotes the note or brand profile evidence cites it, and states other source types cannot be deleted here. It points to list_claims and update_brand_profile as the places to check those conditions, but does not name where non-note sources are deleted.

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

All Mark 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?