Skip to main content
Glama
Sign In
was-fb-mcp

was-fb-mcp

by was-member-keramat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

fb_get_me

Get details of the currently authenticated Facebook user, page, or token owner. Specify fields like id, name, email, or picture.

Instructions

Get details of the currently authenticated Facebook User, Page, or Token owner.

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_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated fields to request (e.g. "id,name,email,picture")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It fails to disclose behavioral traits such as whether the operation is read-only, rate limits, or required permissions. The description is too minimal to inform the agent about side effects or constraints.

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?

The description is a single concise sentence that front-loads the main action. It efficiently communicates the purpose without extraneous words, though it could include more detail without becoming bloated.

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?

Given the tool complexity (single optional parameter, no output schema), the description is adequate but not complete. It does not describe return structure or example fields, leaving the agent to guess what 'details' means. A minimal addition would improve completeness.

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% for the single parameter 'fields', and the schema already describes it well. The description adds no additional meaning beyond the schema, which is acceptable given high coverage. Baseline score of 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?

Description clearly states it retrieves details of the authenticated entity (user, page, or token owner). The verb 'Get' and resource are explicit. While it doesn't differentiate from siblings, the sibling tools have distinct purposes (e.g., fb_reply_comment, fb_list_campaigns), making the distinction clear.

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 guidance on when to use this tool versus alternatives. No mention of prerequisites, or situations where other tools (like fb_api) might be preferred. The description lacks context for decision-making.

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