Skip to main content
Glama
Sign In

InstantClips

by ai.instantclips
OverviewDiscussionsAdmin

Tell the InstantClips team about a problem with these tools

send_feedback

Send the InstantClips team a note about these tools: one that failed or surprised, or something the user wanted that no tool does. Show the user the note and send it only with their OK. Not for support or ratings.

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": {
      "message": "<message>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesWhat happened, what was expected, and the tool and ids involved; leave out personal details it doesn't need.

Output Schema

NameRequiredDescriptionDefault
sentYes
next_stepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only say the call is not read-only and not destructive; the description adds the critical behavioral fact that the message is user-visible and requires user approval before sending, which is a human-in-the-loop constraint not encoded anywhere else. It stops short of saying what happens after submission (confirmation, follow-up), which is left to the output schema.

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 with zero filler: what to send, what qualifies, and the consent step, ordered so the qualifying criteria precede the send instruction. No restatement of the tool name or schema fields.

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?

For a single-required-parameter tool with a full schema and an output schema, everything an agent needs is present: trigger conditions, exclusions, content guidance via the schema, and the mandatory user-approval step.

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 the schema description already spells out what the message should contain (what happened, expected, tool and ids, no personal details). The description adds only the implicit point that the message text is shown to the user, so the schema does the heavy lifting.

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?

The description names a specific verb and recipient ("Send the InstantClips team a note") and scopes the content to tool problems or gaps. This is unmistakably different from every sibling, all of which are brand/product/video operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit triggers (a tool that failed or surprised, or a user need no tool covers) and explicit exclusions ("Not for support or ratings"). It also specifies the consent precondition: show the user the note and send only with their OK.

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

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