Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

slack_delete_message

Delete a message previously posted — by the same author that posted it.

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": {
      "channel": "<channel>",
      "ts": "<ts>"
    },
    "name": "slack_delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
tsYesMessage timestamp returned by `slack_post_message`.
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
authorNoWho writes — `"me"` (as you, user token) or `"app"` (as the Slack app, bot token). Required when the workspace holds both tokens; with a single one, it is used and may be omitted.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
channelYesChannel ID.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one real behavioral constraint — deletion is limited to messages from the same author — which is valuable and not derivable from the schema. However, it omits whether deletion is permanent, whether it removes thread replies, what happens on a permission failure, and whether the operation is idempotent, all of which matter for a destructive mutation.

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?

A single sentence with no filler, and the constraint is front-loaded rather than buried. It is terse to the point that it under-specifies, but nothing in it is wasted wording.

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

Completeness3/5

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

For a destructive mutation with no annotations and no output schema, the definition is thin: it does not say whether the delete is reversible, what the result looks like, or how failures surface. The authorship clause covers the most important eligibility rule, which keeps it above inadequate, but an agent still lacks enough context to predict outcomes.

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%, so channel, ts, author and the _org/_group/_project/_instance/_run_id context parameters are already documented in the schema. The description adds only the indirect hint that the ts must come from a previously posted message. Baseline 3 applies when the schema does the documentation work.

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 a message") plus the scope constraint that the target must have been "previously posted." The clause "by the same author that posted it" distinguishes it from slack_post_message and from any moderation-style delete, so an agent can identify the operation without opening the schema.

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?

Usage is only implied: an agent infers it should call this when it wants to remove a message it posted. There is no explicit when-to-use block, no statement of what to do when the message was authored by someone else, and no named alternative or precondition (e.g. what to do instead if deletion is not permitted).

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

All Tulina 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