Skip to main content
Glama
Sign In

KonbiniAPI MCP

by com.konbiniapi
OverviewDiscussionsAdmin

X: Get community media

x_get_community_media
Read-onlyIdempotent

Returns public posts from an X community's Media tab. 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": {
      "communityId": "<communityId>"
    },
    "name": "x_get_community_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoMaximum number of media posts to return from the community media timeline (maximum: 100) Default: 40
cursorNonextCursor from the previous page. Omit for the first page
communityIdYesX community ID
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. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, covering the safety profile. The description adds that posts are public and that projection parameters reduce payload size, which is useful context. It does not disclose return format, pagination behavior, or rate limits, so the added behavioral value is modest.

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 two sentences with no wasted words. The primary purpose and scope are front-loaded, followed immediately by the optional payload-reduction parameters. Every sentence earns its place.

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 annotations covering safety and schema covering all parameters, the description is nearly complete for a read-only list tool. It states what is returned and why the projection parameters exist. Without an output schema, it could say more about response shape or pagination, but the essentials are present.

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 description coverage is 100%, so the baseline is 3. The description still adds meaning by grouping projection_preset, data_fields, and item_fields together as payload reduction mechanisms, clarifying their shared output-shaping purpose beyond individual schema entries. It does not add detail for cursor, count, or communityId, which the schema already covers.

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 and resource: 'Returns public posts from an X community's Media tab.' It clearly distinguishes the tool from siblings like x_get_community_posts and x_get_community by scoping it to the Media tab. An agent can identify its purpose without opening the schema.

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

Usage Guidelines3/5

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

The description implies usage by specifying that it returns posts from a community's Media tab. However, it does not explicitly say when to use this tool versus x_get_community_posts or other siblings, nor does it mention exclusions or prerequisites. Usage is inferable but not guided.

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