Skip to main content
Glama
Sign In
Heartran

Kanka MCP Server

by Heartran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_items

Lists campaign items with pagination and entry filtering so you can fetch only records with empty or filled entries and optionally omit long entry text to shrink responses.

Instructions

List items. Use per_page to keep responses small enough to be returned whole, and entry_filter to return only records whose entry is empty or filled.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
entriesNoInclude full entry/entry_parsed text (default true). Set false to omit the long entry fields, shrink the response, and get a has_entry boolean per record instead.
per_pageNoRecords per page, 1-100. Enforced by this server, so it holds even when the Kanka API returns a different page size. Omit to return the API's own page untouched; when set (or when entry_filter is used) the default is 25 with entries, 100 without.
campaignIdYes
entry_filterNoKeep only records with an empty entry ('empty'), only records with text ('filled'), or all of them ('all', default). Filtering is applied across the whole collection, not just one API page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.0
    • addedInput schema / properties / entries
      Added value: +{
+  "description": "Include full entry/entry_parsed text (default true). Set false to omit the long entry fields, shrink the response, and get a has_entry boolean per record instead.",
+  "type": "boolean"
+}
    • addedInput schema / properties / entry_filter
      Added value: +{
+  "description": "Keep only records with an empty entry ('empty'), only records with text ('filled'), or all of them ('all', default). Filtering is applied across the whole collection, not just one API page.",
+  "enum": [
+    "all",
+    "empty",
+    "filled"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / page / description
      Added value: +"Page number (default 1)."
    • addedInput schema / properties / per_page
      Added value: +{
+  "description": "Records per page, 1-100. Enforced by this server, so it holds even when the Kanka API returns a different page size. Omit to return the API's own page untouched; when set (or when entry_filter is used) the default is 25 with entries, 100 without.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "number"
+}
  2. First observedv2.1.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully hints at a response-size/truncation concern ("small enough to be returned whole"), which is real value beyond the schema, but it says nothing about permissions, ordering, or what a record contains.

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 short sentences, purpose front-loaded, no filler. Every clause references a concrete parameter and its benefit.

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

Completeness3/5

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

With five parameters, no annotations, and no output schema, the description should do more. It covers the pagination trade-off but omits the required campaignId, says nothing about ordering or what fields a record returns, and does not explain the interaction between entries=false and entry_filter.

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 80%, so the baseline is 3. The description restates what per_page and entry_filter already document in the schema and adds no syntax or interaction detail; page, entries, and campaignId are not touched at all.

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 ("List items") that matches the naming pattern of siblings like list_characters and list_locations, so the agent can infer the entity type. It does not explicitly distinguish this tool from search or get_item, but the list-vs-get split is conventional.

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?

Gives practical guidance on how to use two parameters (per_page to keep responses whole, entry_filter to restrict by entry state), which is genuinely actionable. However, it never says when to choose this tool over siblings such as search or the per-entity list_* tools, leaving the routing decision implicit.

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

Deploy Server

Other Tools