Skip to main content
Glama
Sign In

Fahi-Videos MCP Server

by io.github.khondokartowsif171
OverviewDiscussionsAdmin

fahi_crm_leads

[100% FREE — Zero API Key Needed] List or add customer leads in the Bangladeshi Customer Care & Order Pipeline.

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": {
      "action": "<action>"
    },
    "name": "fahi_crm_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional customer context or order notes.
phoneNoInternational phone number in E.164 format, e.g. +8801712345678 (required when action="add").
actionYesList current leads & call stats or add a new lead.
productNoProduct or campaign name (required when action="add").
customerNameNoCustomer full name (required when action="add").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it only discloses cost/auth ('100% FREE — Zero API Key Needed'). It never states that 'add' is a persistent write, whether duplicates are rejected or merged, whether 'list' paginates or caps results, or what a call returns.

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 front-loaded sentence with the differentiator (free, no key) in brackets first and the capability second. It is short and has no filler, though the bracketed tag is arguably marketing rather than call-relevant information.

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

Completeness2/5

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

For a five-parameter, annotation-free tool with no output schema, the description says nothing about the shape of returned leads/stats, pagination, or write-side effects. An agent could invoke it but cannot predict what it will get back or what 'add' does to existing data.

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 every parameter, including the action enum and the action-conditional requirements, is already documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 specific verbs (list/add) and the resource (customer leads) plus the domain scope (Bangladeshi Customer Care & Order Pipeline), which is unambiguous enough to separate it from the media-generation siblings. It loses a point only because the dual list/add nature isn't resolved in the description itself.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says when to pick 'list' versus 'add', no prerequisites, and no mention of what to do if a lead already exists. The only usage signal is the word 'or', so an agent must infer selection purely from the action enum in the schema.

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

All Fahi-Videos MCP Server 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