Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Facebook profile

facebook_profile_get
Read-onlyIdempotent

Look up a Facebook profile or Page by URL or username to fetch public details, including optional business hours when available.

Instructions

Get a Facebook profile or Page by URL or username. Requires url.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_profile_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Facebook public profile or page URL to look up.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.
includeBusinessHoursNoOptional: include structured business hours in the response when available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds essentially nothing beyond that — no note on rate limiting, authentication, what an unknown profile returns, or what fields the response contains. Worse, "or username" implies an input flexibility the schema does not grant, creating ambiguity about the accepted value form.

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 sentences with the resource scoping front-loaded and no filler. The second sentence is largely redundant with the schema's required array, which is a minor waste rather than a structural flaw.

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?

For a simple read tool with rich annotations and full schema coverage, the definition is minimally viable: an agent knows the resource and the key input. It is incomplete in that no return shape is disclosed (there is no output schema) and the input-form ambiguity around username vs URL is left unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline would be 3, but three of five parameters (context, llm_model, conversation_id) are never acknowledged and the one parameter mentioned is described in a way that conflicts with its schema wording (URL only vs "URL or username"). The single sentence about `url` duplicates the required-flag already in the schema rather than clarifying format or accepted variants.

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 names a specific verb and resource ("Get a Facebook profile or Page") and implicitly distinguishes itself from the list-oriented siblings such as facebook_profile_posts_list and facebook_profile_photos_list. The trailing "Requires `url`" restates schema facts rather than adding scope, and the phrase "or username" is not matched by the schema, which describes the value only as a URL.

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 statement of when to call this versus siblings like facebook_group_get, facebook_event_get, or the profile sub-lists, and no exclusions or prerequisites. An agent must infer that this fetches a page-level profile while the *_list tools fetch associated collections.

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

Deploy Server

Other Tools