Skip to main content
Glama
daikazu

Rybbit MCP Server

by daikazu

rybbit_delete_funnel

Permanently delete a saved funnel from Rybbit Analytics by providing the site ID and funnel ID.

Instructions

Delete a saved funnel permanently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID or identifier
funnelIdYesFunnel identifier
Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It states the deletion is 'permanently', which is a key behavioral trait (irreversible). However, it does not mention potential side effects, required permissions, or what happens to associated data, leaving gaps in transparency.

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?

The description is a single, clear sentence that is front-loaded with the primary action. It contains no filler or redundant information, earning full marks for conciseness and structure.

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?

This is a simple delete operation with a clear action and permanent nature, which is adequately described. There is no output schema, but for a delete tool the return format is often trivial; the description is sufficient for the tool's complexity, though it could mention return values or confirmation.

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%, with both siteId and funnelId having basic descriptions. The tool description adds no additional meaning beyond the schema, so it matches the baseline for adequate but unenhanced parameter semantics.

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 'Delete a saved funnel permanently' uses a specific verb (Delete), identifies the resource (saved funnel), and adds the critical qualifier 'permanently', distinguishing it from other funnel-related tools like create/update/analyze. There is no ambiguity about what the tool does.

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 description does not explicitly state when to use this tool versus alternatives, but the name and action make it clear that it is for deleting funnels. No exclusions or preconditions are mentioned, so guidance is implied rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/daikazu/rybbit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server