Skip to main content
Glama

social-media-video-downloader

Get Facebook Profile Details (Price:3)

get_facebook_v3_profile_details

Retrieves the profile details for 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_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the Facebook profile.

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?

No annotations are supplied, so the description carries the full behavioral burden, yet it only discloses the billing cost ('3 Credits' per call) and a 'Facebook-Profile' grouping label. It does not state whether failed calls are billed, what authentication or quota constraints apply, or what shape 'profile details' takes, all of which matter for a paid read endpoint.

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?

Three short sentences, front-loaded with the action and resource, with no redundant prose. The 'Group: Facebook-Profile' fragment is minor internal metadata that does not help an agent decide or invoke, but it costs little.

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 no nested objects and no output schema, so the description need not explain return values. Still, given zero annotations, it should say more about what 'profile details' includes and how it differs from the many adjacent Facebook profile tools; as written it is merely adequate.

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?

With a single required parameter and 100% schema description coverage, the schema already documents the URL field and even provides an example. The description's phrase 'for a given Facebook profile URL' merely echoes that, adding no format, normalization, or accepted-URL-variant guidance. Baseline 3 is appropriate.

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?

The description states a specific verb and resource: 'Retrieves the profile details' for a 'Facebook profile URL.' That is clearly distinguishable in isolation, but it offers no differentiation from close siblings such as get_facebook_v3_profile_about, get_facebook_v3_profile_photos, or get_facebook_v3_profile_id, leaving the agent to guess which profile endpoint returns what.

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 or when-not-to-use guidance and no mention of alternatives; the agent is expected to infer routing from the tool name alone. Nothing indicates prerequisites such as the profile being public or the URL needing to be a canonical profile (not group/post) URL.

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