Skip to main content
Glama

List Facebook profile posts

facebook_profile_posts_list
Read-only

List posts from a Facebook profile or Page. Accepts a profile URL or page id. Credits: 1 base; hostMedia=true adds +2 per hosted asset (up to 24 / 49 max). Failed assets are not surcharged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFull public Facebook profile or page URL.
linkNoAlias for `url`. Prefer `url`.
pathNoAlias for `url`. Prefer `url`.
trimNoIgnored if this tool does not support it.
limitNoIgnored if this tool does not support it.
cursorNoOpaque pagination cursor from a previous response.
offsetNoIgnored if this tool does not support it.
pageIdNoFacebook page or profile id when you have it instead of a full URL.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
tweetIdNoAlias for `url`. Prefer `url`.
pageSizeNoIgnored if this tool does not support it.
tweetUrlNoAlias for `url`. Prefer `url`.
tweet_idNoAlias for `url`. Prefer `url`.
hostMediaNoWhen true, hosts source media for 90 days and returns delivery URLs in each post's `hostedMedia`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
permalinkNoAlias for `url`. Prefer `url`.
tweet_urlNoAlias for `url`. Prefer `url`.
maxResultsNoIgnored if this tool does not support it.
max_resultsNoIgnored if this tool does not support it.
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. Changed19 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / link / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / link / type
      Removed value: -"string"
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / max_results
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / pageSize
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / path
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Alias for `url`. Prefer `url`."
      +}
    • addedInput schema / properties / permalink / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / permalink / type
      Removed value: -"string"
    • addedInput schema / properties / trim
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / tweetId / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweetId / type
      Removed value: -"string"
    • addedInput schema / properties / tweetUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweetUrl / type
      Removed value: -"string"
    • addedInput schema / properties / tweet_id / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweet_id / type
      Removed value: -"string"
    • addedInput schema / properties / tweet_url / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweet_url / type
      Removed value: -"string"
  2. Changed6 schema fields changed
    • addedInput schema / properties / link
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / permalink
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweetId
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweetUrl
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweet_id
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweet_url
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
  3. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo 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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "context",
      +  "llm_model"
      +]
  4. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Changed1 schema field changed
    • addedInput schema / properties / hostMedia
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "0",
      +        "1",
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ],
      +  "description": "When true, hosts source media for 90 days and returns delivery URLs in each post's `hostedMedia`."
      +}
  6. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  7. Changed1 schema field changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque pagination cursor from a previous response (`data.page.nextCursor`)."New value: +"Opaque pagination cursor from a previous response."
  8. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a concrete cost model (1 base credit, +2 per hosted asset with caps, no charge for failed assets), which materially affects selection. It does not mention pagination or rate limits, but those are less critical given the read-only annotation.

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?

The description is three short sentences that front-load the purpose, then cover input, then cost. Each sentence earns its place with no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with 20 parameters, many marked as generic aliases or 'ignored if not supported', and no output schema, the description leaves gaps. It does not explain pagination via cursor, which parameters actually work (e.g., limit, offset), or what the response contains. The agent must rely on the schema for required parameters like context and llm_model, and even then some ambiguity remains.

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?

The description adds meaning by explicitly saying it accepts a profile URL or page id (url/pageId) and by explaining the behavioral effect of hostMedia (credit surcharge). Most other parameters are generic aliases or 'Ignored if not supported' in the schema, and the description does not clarify which are honored. With 100% schema coverage on paper, the baseline is 3.

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 states a specific verb ('List') and resource ('posts from a Facebook profile or Page'), which distinguishes it from siblings like facebook_group_posts_list and facebook_profile_photos_list. It also clarifies that both profiles and Pages are valid targets, and mentions accepting a URL or page id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly scopes the tool to Facebook profiles and Pages, implying that group posts are handled by a sibling. However, it does not explicitly name alternative tools or state exclusions (e.g., public vs private profiles). The credit note adds operational context for when to use the tool cost-effectively.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.