Influship

get_posts

Read-only

Fetch a creator's posts, sorted and paginated.

Use this when the user asks to see what a creator has posted (e.g., "show me Jane's last 20 posts", "what are this creator's top-engagement reels?", "pull recent posts from creator-id ABC"). Identify the creator by either creator_id (UUID) OR (platform + username).

sort defaults to "recent" (newest first); use "top_engagement" for the highest- engagement posts, or one of "most_likes" / "most_views" / "most_comments" for a specific metric. limit defaults to 12 and is capped at 50. Pass cursor from a previous response's next_cursor to paginate.

Returns post records (caption, media URL, like/comment/view counts, timestamps), plus has_more and next_cursor for pagination.

Examples:

User: "Show @niickjackson's recent Instagram posts" -> use this tool with platform "instagram" and username "niickjackson".
User: "Is @niickjackson a fit for Pixel?" -> use this after get_profile when the fit analysis needs recent content evidence, then call match_creators.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	Sort order	recent
`limit`	No	Maximum posts to return
`cursor`	No	Opaque keyset cursor from next_cursor. A cursor is bound to the sort order that produced it; using it with another sort returns 400.
`platform`	No	Platform (required with username)
`username`	No	Username (required with platform)
`creator_id`	No	Creator ID (use this OR platform+username)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`data`	No
`count`	No
`results`	No
`has_more`	No
`not_found`	No
`next_cursor`	No
`suggested_followups`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 9, 2026

changedInput schema / definitions / PostSort / description

Previous value: -"Sort order for posts"New value: +"Stable post ordering. top_engagement uses (likes + comments) / views, with posts that have no measurable views sorted last."

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor for next page"New value: +"Opaque keyset cursor from next_cursor. A cursor is bound to the sort order that produced it; using it with another sort returns 400."

First observedMay 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds rich behavioral context beyond the read-only annotation: describes pagination via next_cursor/has_more, limit cap at 50, default sort behavior, and cursor-tied-to-sort error semantics. This gives an agent a clear model of how the tool behaves and what to expect.

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?

Though moderately long, the description is well-structured with a clear lead sentence, parameter guidance, return summary, and concrete examples. Every section adds value and none feels redundant with the schema.

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

Completeness5/5

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

For a list tool with pagination, multiple sort modes, and an OR identifier pattern, the description fully covers identification, sorting defaults, pagination semantics, and return fields. Output schema handles structured return details, and the description supplements with usage context and examples.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds crucial meaning: the OR relationship between creator_id and (platform+username), the semantics behind each sort enum value, and how to use cursor from next_cursor. This goes beyond the schema's field-level descriptions.

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?

The description opens with a specific verb and resource ('Fetch a creator's posts, sorted and paginated'), making the core purpose clear. However, it does not explicitly distinguish this tool from sibling get_instagram_posts, so it misses the sibling-differentiation criterion for 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 Guidelines4/5

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

Provides explicit usage scenarios and examples ('Use this when the user asks to see what a creator has posted'), plus sequencing guidance with get_profile and match_creators. It lacks clear when-not-to-use or alternative-tool exclusions, so it earns 4 rather than 5.

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

All Influship tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.