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

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

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.

Changed4 schema fields changedOct 23, 2026

addedInput schema / $ref

Added value: +"#/definitions/GetPostsQuery"

addedInput schema / definitions / GetPostsQuery

Added value: +{
+  "properties": {
+    "creator_id": {
+      "description": "Creator ID (use this OR platform+username)",
+      "example": "123e4567-e89b-12d3-a456-426614174000",
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    "cursor": {
+      "description": "Opaque keyset cursor from next_cursor. A cursor is bound to the sort order that produced it; using it with another sort returns 400.",
+      "type": "string"
+    },
+    "limit": {
+      "default": 12,
+      "description": "Maximum posts to return",
+      "example": 12,
+      "maximum": 50,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "platform": {
+      "allOf": [
+        {
+          "$ref": "#/definitions/Platform"
+        }
+      ],
+      "description": "Platform (required with username)"
+    },
+    "sort": {
+      "allOf": [
+        {
+          "$ref": "#/definitions/PostSort"
+        }
+      ],
+      "default": "recent",
+      "description": "Sort order"
+    },
+    "username": {
+      "description": "Username (required with platform)",
+      "example": "fitness_coach_jane",
+      "maxLength": 50,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds the limit cap of 50 and cursor-bound-to-sort behavior, which are meaningful constraints. It does not disclose rate limits, auth requirements, or the notable fact that only Instagram is currently a valid platform despite the generic tool name.

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?

Front-loaded with the verb and resource, then organized into usage, parameter notes, return shape and examples. Slightly redundant with the schema on defaults, caps and the cursor rule, and the return-value sentence is unnecessary given an output schema exists.

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?

Covers identification, sorting, pagination and workflow placement well, and the output schema plus annotations carry return format and safety. The gap is the Platform enum being Instagram-only, which an agent could miss given the generic name and heading into a 400.

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 description coverage is 100%, so all six parameters are already documented, and most of the description's parameter text (defaults of 12 and "recent", the 50 cap, cursor binding) restates the schema. The one added value is framing the identifier as creator_id OR platform+username in prose, which is a marginal gain over the schema.

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?

States a specific verb and resource ("Fetch a creator's posts"), plus the sorted/paginated modifiers that define scope. It is clearly distinct from transcript/profile siblings, though it never explains how it relates to the platform-specific siblings like get_instagram_posts or list_tiktok_profile_videos that overlap heavily with it.

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?

Gives an explicit triggering condition ("Use this when the user asks to see what a creator has posted") plus three concrete example utterances, and even places itself in a workflow after get_profile and before match_creators. It stops short of stating when NOT to use it, e.g. when a platform-specific sibling is preferable.

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.