Skip to main content
Glama
Sign In
Senja MCP Server

Senja MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete one testimonial

delete_testimonial
Destructive

Permanently remove a specific Senja testimonial by ID after explicit confirmation. Use this irreversible action only when the user requests exactly that deletion.

Instructions

Permanently delete exactly the requested testimonial. Irreversible; confirmation required.

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": {
      "testimonial_id": "<testimonial_id>"
    },
    "name": "delete_testimonial"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoExact configured private account profile label; not a tenant or provider account ID.
confirmNoSet true only when the user asked for exactly this action.
testimonial_idYesExact testimonial ID. No slash, traversal or arbitrary URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for the requested mutation or exclusive private output file."New value: +"Set true only when the user asked for exactly this action."
  2. First observedv2.0.0

TDQS

A3.8/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 covered structurally. The description adds real value beyond that: permanence, irreversibility, and a mandatory confirmation gate before the delete proceeds.

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?

Two short sentences, front-loaded with the destructive verb and scope, with zero filler. Every clause carries information an agent needs before calling.

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 single-record delete with no output schema, the description plus annotations cover action, scope, reversibility, and the confirmation requirement. It omits edge behavior such as what happens when the ID does not exist, but that is a minor gap for this complexity.

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 schema already documents account, confirm, and testimonial_id semantics in detail. The description only echoes the 'exactly the requested' scoping and confirmation requirement, adding little beyond the schema. Baseline 3 is appropriate.

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 ('Permanently delete... testimonial') with a scoping qualifier ('exactly the requested'). An agent can distinguish it from update_testimonial and create_testimonial without opening the schema, though no sibling is named explicitly.

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?

'Confirmation required' implies a precondition for use, and 'exactly the requested' hints at a no-bulk scope, but there is no explicit when-to-use/when-not guidance and no alternative tool is named for softer or reversible removal.

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