Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd

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.
cursorNoOpaque pagination cursor from a previous response.
pageIdNoFacebook page or profile id when you have it instead of a full URL.
hostMediaNoWhen true, hosts source media for 90 days and returns delivery URLs in each post's `hostedMedia`.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations provide readOnlyHint and openWorldHint, but the description adds valuable context: the credit cost structure (1 base, +2 per hosted asset) and the behavior that failed assets are not surcharged. This goes beyond annotations and helps the agent anticipate costs and 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?

Two concise sentences with no filler. The primary purpose is front-loaded, then cost details are provided. Minimal but complete.

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

Completeness4/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 no output schema, the description covers input selection, cost behavior, and the hostMedia option. Pagination is not mentioned, but the cursor parameter is in the schema, so the agent can infer it. Sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are fully documented. The description adds meaning by clarifying that url and pageId are alternatives for specifying the target, and explains the hostMedia effect (hosts for 90 days, adds cost). This enhances the schema.

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 'List posts from a Facebook profile or Page' – a specific verb and resource. It distinguishes from sibling tools like facebook_group_posts_list and facebook_profile_photos_list by explicitly mentioning profile/Page scope. Also clarifies the input methods (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 specifies that this tool is for profiles or Pages, which implicitly distinguishes it from group posts or other list tools. It also explains the URL/pageId alternatives. However, it doesn't explicitly say when not to use it or name alternative tools, but the scope is clear enough.

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

All Social Fetch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation5/5

Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.

Naming Consistency5/5

All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).

Tool Count2/5

The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.

Completeness4/5

The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.

Resources