Skip to main content
Glama

social-media-video-downloader

Get Facebook Profile Reels (Price:3)

get_facebook_v3_profile_reels

Retrieves the reels from a given Facebook profile URL. Group: Facebook-Profile. Billing per call: 3 Credits.

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": {
      "url": "<url>"
    },
    "name": "get_facebook_v3_profile_reels"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the Facebook profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 behavioral burden. It does add one genuinely useful piece of context beyond the schema: a billing cost of 3 credits per call, which affects invocation planning. However, it says nothing about pagination, result limits, whether private profiles return empty sets, or authentication requirements for a retrieval tool.

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?

Two short, front-loaded sentences with zero filler in the operational sentence. 'Group: Facebook-Profile' is catalog metadata that adds little for an agent, while the billing sentence is actionable and should stay. Nothing is padded, but one clause is arguably dead weight.

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?

This is a simple one-parameter read tool with a fully documented schema and no output schema, so the description is close to sufficient. It still leaves open what a returned reel contains and whether results are paginated or capped, both of which an agent would want before calling for a large profile.

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 there is a single required parameter fully documented with an example, so the baseline is 3. The description's phrase 'from a given Facebook profile URL' mirrors the schema rather than adding constraints such as accepted URL forms or profile-vs-page distinctions.

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: retrieves reels from a given Facebook profile URL. Combined with the tool name, an agent can tell it apart from profile_photos, profile_about, or post_details siblings. It stops short of explicitly naming what it does not cover, so it is clear but not fully differentiated.

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 by the phrase 'reels from a given Facebook profile URL' - there is no statement of when to prefer this over profile_photos or post_details, and no prerequisites or exclusions. The mapping of URL-in, reels-out is enough for an agent to infer the call context, but no explicit guidance is provided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources