Mentio

Delete activity

delete_activity

Destructive

Delete an outreach activity logged by mistake. The person's owner and stage stay as they are. An activity logged in a keyword group is found with that groupId.

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

Input Schema

Name	Required	Description
`id`	Yes	Person id (aut_...)
`groupId`	No	Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace.
`activityId`	Yes	Activity id (act_...), from list_activities
`idempotencyKey`	No	Optional. A unique value (a UUID) for this call: 1 to 255 visible ASCII characters, no spaces. Calling again with the same key and the same input within 24 hours returns the first result instead of doing it twice.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Optional. A unique value (a UUID) for this call: 1 to 255 visible ASCII characters, no spaces. Calling again with the same key and the same input within 24 hours returns the first result instead of doing it twice.",
+  "maxLength": 255,
+  "minLength": 1,
+  "pattern": "^[\\x21-\\x7e]+$",
+  "type": "string"
+}

Changed1 schema field changedOct 12, 2026

changedInput schema / properties / groupId / description

Previous value: -"Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, merges, activities and segments. Omit for the whole workspace."New value: +"Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, mute, merges, activities and segments. Omit for the whole workspace."

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / groupId

Added value: +{
+  "description": "Scope to one keyword group (grp_...): only people who mentioned that group's keywords, with that group's own tags, notes, merges, activities and segments. Omit for the whole workspace.",
+  "minLength": 1,
+  "type": "string"
+}

First observedOct 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is known. The description adds real value beyond that by bounding the blast radius ('the person's owner and stage stay as they are') and by explaining the group scoping needed to locate a group-logged activity. It still omits what else the deletion affects, such as analytics counts or reporting aggregates.

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, front-loaded with the action and the intended use, followed by the two facts that actually change caller behavior. Nothing is repeated from the schema or annotations.

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 two-required-parameter delete with no output schema, the definition covers intent, side-effect scope, and group addressing, which is most of what an agent needs. The remaining gap is whether the deletion is reversible or can be re-logged, and whether dependent counts are recalculated.

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%, so all four parameters are already documented, giving a baseline of 3. The description still earns credit by clarifying a non-obvious lookup rule: an activity logged inside a keyword group must be addressed with that groupId, which is semantic guidance the schema's generic scope text does not spell out.

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 ('Delete an outreach activity') and narrows intent to activities 'logged by mistake', which separates it from log_activity at a glance. It does not explicitly name the sibling it complements, so it stops short of full differentiation.

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?

The phrase 'logged by mistake' implies the intended use case (cleanup of erroneous logs) and the schema points to list_activities for obtaining activityId. However, there is no explicit when-not-to-use guidance, no statement that this should not be used to correct rather than remove records, and no named alternative.

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

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