Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Facebook group

facebook_group_get
Read-onlyIdempotent

Fetch a public Facebook group by URL or numeric group ID to retrieve group information for social research, monitoring, or analysis.

Instructions

Get a Facebook group by URL or group id. Optional inputs: url and groupId.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPublic Facebook group URL.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
groupIdNoNumeric Facebook group id when you have it instead of a full URL.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is fully covered. The description adds no behavioral context beyond restating parameter names — nothing about failure modes, private/inaccessible groups, or the fact that exactly one identifier is effectively needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and earns its place, but the second sentence ("Optional inputs: `url` and `groupId`.") only repeats what the schema already declares and could be cut or replaced with genuinely useful guidance.

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 annotations covering safety and 100% schema coverage, little is required. However, the ambiguity of two mutually substitutable identifiers and the complete absence of any return-value indication (no output schema) leave gaps the description could have closed in one clause.

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%, so both `url` and `groupId` are already documented with format hints. The description merely echoes their names and optionality, adding no selection logic (e.g. prefer groupId when known) beyond the schema.

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 ("Get a Facebook group") with the identifying keys, so it is clearly a single-object fetch, distinct from sibling list tools like facebook_group_posts_list. It stops short of naming any sibling explicitly.

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?

No when-to-use guidance, no preconditions, and no rule for what to do if the caller has both a URL and a numeric id, or neither. The agent must infer lookup behavior entirely from the schema.

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