Skip to main content
Glama
Sign In

KonbiniAPI MCP

by com.konbiniapi
OverviewDiscussionsAdmin

X: Get user posts

x_get_user_posts
Read-onlyIdempotent

Returns public posts from a user's profile. This feed is not guaranteed to be chronological and is often a ranked public selection. Pages may overlap: a pinned post is repeated on every page, so deduplicate by id when paging. Supports projection_preset, data_fields, and item_fields for payload reduction.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "x_get_user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNonextCursor from the previous page. Omit for the first page
usernameYesX username (with or without @ symbol)
data_fieldsNoOptional. Add top-level data keys on top of the selected projection_preset.
item_fieldsNoOptional. Add item keys from data.orderedItems[] on top of the selected projection_preset.
projection_presetNoOptional. Defaults to "minimal". Use one of: full, minimal, identity, engagement, or content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor"New value: +"nextCursor from the previous page. Omit for the first page"
    • changedInput schema / properties / item_fields / items / enum
      Previous value: -[
-  "type",
-  "id",
-  "url",
-  "entityId",
-  "content",
-  "published",
-  "likeCount",
-  "replyCount",
-  "viewCount",
-  "repostCount",
-  "quoteCount",
-  "saveCount",
-  "contentFormat",
-  "isEdited",
-  "attributedTo",
-  "inReplyTo",
-  "quote",
-  "image",
-  "attachment",
-  "tag"
-]New value: +[
+  "permission",
+  "type",
+  "id",
+  "url",
+  "entityId",
+  "content",
+  "published",
+  "likeCount",
+  "replyCount",
+  "viewCount",
+  "repostCount",
+  "quoteCount",
+  "saveCount",
+  "contentFormat",
+  "language",
+  "isAdult",
+  "isEdited",
+  "attributedTo",
+  "inReplyTo",
+  "context",
+  "audience",
+  "quote",
+  "image",
+  "attachment",
+  "tag",
+  "generator"
+]
  2. Changed2 schema fields changed
    • removedInput schema / properties / count
      Removed value: -{
-  "description": "Maximum number of posts to return from the public profile selection (maximum: 100) Default: 20",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Pagination cursor",
+  "type": "string"
+}
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, but the description adds genuinely non-obvious behavior: the feed is not chronological, is often a ranked selection, and pages overlap because a pinned post repeats on every page. That dedupe-by-id instruction is exactly the kind of trait annotations cannot express. It stops short of rate limits, auth requirements, or page-size behavior, so not a 5.

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?

Four sentences, purpose first, then the two behavioral warnings, then the payload-reduction note. No filler and no repetition of the title or schema.

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?

With no output schema, the description still conveys the shape of the return (public posts, paged, possibly non-chronological, dedupe required) and all five parameters are documented in the schema. It omits pagination termination and any auth/paywall caveats, but the core calling information is present.

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 the baseline is 3. The description adds one piece of meaning the schema lacks — that projection_preset, data_fields, and item_fields exist for payload reduction — but says nothing about cursor semantics or default preset behavior beyond what the schema already states.

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: returns public posts from a user's profile. That is unambiguous against x_get_post (single post), but it never names or contrasts with the closest siblings such as x_get_user_highlights or x_get_community_posts, so an agent must infer the boundary itself.

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 when-to-use or when-not guidance relative to the many sibling post-listing tools (x_get_user_highlights, x_get_community_posts, x_get_post). The paging/dedupe advice is operational guidance for using the result, not guidance on tool selection, which is what this dimension measures.

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

All KonbiniAPI MCP toolsInspect
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.

Resources