Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kickstarter_discover

Browse or search Kickstarter's Discover campaigns by category, keyword, sort, state, or staff picks. Returns funding, creator, location, category, and cover photo details.

Instructions

Browse or search Kickstarter's Discover surface. Returns one page of Kickstarter's own Discover results -- browse by category id and/or a free-text search term, sorted by magic/popularity/newest/end_date/most_funded, optionally filtered by campaign state and/or restricted to staff picks. Each result includes the campaign's funding snapshot (goal, pledged, percent funded, backers), category, location, creator, and cover photo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number
sortNoResult order
termNoFree-text search query
stateNoRepeatable campaign state filter
category_idNoKickstarter's own numeric category id (top-level or sub-category), e.g. 16 for Technology
staff_pick_onlyNoRestrict results to Kickstarter's own \

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "magic",
+  "popularity",
+  "newest",
+  "end_date",
+  "most_funded"
+]
    • addedInput schema / properties / state / items
      Added value: +{
+  "enum": [
+    "upcoming",
+    "live",
+    "late_pledge",
+    "canceled",
+    "failed",
+    "successful"
+  ],
+  "type": "string"
+}
  2. Addedv1.16.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool returns one page of results and enumerates the result fields (funding snapshot, category, location, creator, cover photo). It does not explicitly mention read-only status, auth requirements, or default behavior with no parameters, but the browse/search framing makes the non-mutating nature clear.

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 filler. The main purpose is front-loaded, and the second sentence compactly enumerates filters and result fields, making every sentence earn 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?

For a 6-parameter read-only browse tool with no output schema, the description covers all major parameters and return contents. It does not mention pagination defaults, the meaning of the page parameter beyond schema, or explicit read-only behavior, but the schema covers parameter details and the description provides enough context for correct invocation.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining combination semantics ('browse by category id and/or a free-text search term'), the meaning of sort options, and the optional state and staff-pick filters. It also compensates for the truncated staff_pick_only schema description.

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 states a specific verb and resource: 'Browse or search Kickstarter's Discover surface' and clarifies it returns one page of results. It is clear about what the tool does, though it does not explicitly differentiate it from sibling Kickstarter tools like kickstarter_project or kickstarter_comments.

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?

The description provides clear context for when to use the tool: browsing or searching Discover by category, free-text term, sort order, campaign state, and staff-pick restriction. It does not explicitly name alternatives or state when not to use it, but the context is sufficient for an agent to infer appropriate usage.

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