Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_get_page_info

Read-only

Retrieves a Facebook Page's core profile details—name, likes, followers, link, about, category, and picture—using a Page ID and access token.

Instructions

Get Page details: name, likes (fan_count), followers, link, about, category, picture.

:param page_id: Optional Page id; defaults to FB_PAGE_ID. :param page_access_token: Optional Page token; defaults to FB_PAGE_ACCESS_TOKEN.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fb_get_page_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idNo
page_access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered structurally. The description adds useful behavior the annotations don't: the exact fields returned and that credentials silently fall back to FB_PAGE_ID / FB_PAGE_ACCESS_TOKEN environment variables. It says nothing about token scopes required or rate/error behavior for an open-world API call.

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?

Front-loaded with the purpose and returned fields in one line, followed by two compact parameter notes; no filler. The raw Sphinx ":param" formatting is slightly unpolished but costs no clarity.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile, keeping the burden low. Still missing for a credential-bearing Facebook API call is any note about required token permissions or failure modes when the fallback env vars are absent.

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 0%, so the description must carry the load, and it does explain both parameters including their environment-variable fallbacks, which the schema alone does not convey. However, it gives no format guidance for page_id or any indication of what permissions the page_access_token must hold, so the compensation is partial.

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+resource ("Get Page details") and enumerates the returned fields (name, fan_count, followers, link, about, category, picture), which makes it clearly a Page-metadata read rather than an insights or posts tool like its siblings. It stops short of naming a sibling it is distinct from, so a 4 rather than a 5.

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 or when-not-to-use guidance is given; nothing tells the agent to prefer this over fb_get_page_insights or fb_list_pages, or what precondition (e.g., an existing Page id) selects it. The only contextual note is parameter defaults, which is not usage guidance.

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