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

was-fb-mcp

by was-member-keramat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

fb_list_pages

Retrieve a list of Facebook Pages managed by the authenticated user.

Instructions

List Facebook Pages managed by the authenticated user.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated fields (default: "id,name,access_token,category,tasks")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

B3.3/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 only mentions 'managed by the authenticated user' implying authentication, but lacks details on authentication requirements, rate limits, or any side effects.

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

Conciseness5/5

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

Single sentence, front-loaded with the action and resource. No unnecessary words or repetition.

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 list tool with 0 required params and no output schema, the description is minimal but sufficient. However, it lacks context about possible return values or pagination, which could help agents adapt.

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%, so baseline is 3. The description does not add any information beyond the schema's parameter description. No additional context for the optional 'fields' parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and resource ('Facebook Pages') with a specific scope ('managed by the authenticated user'). It distinguishes itself from sibling tools like fb_list_ad_accounts or fb_list_campaigns.

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 vs alternatives, or any prerequisites. The description simply states what it does without contextual usage advice.

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