Skip to main content
Glama
Sign In

Jam

by dev.jam
OverviewDiscussionsAdmin

listJams

Read-onlyIdempotent

Deprecated: use searchJams instead. Lists Jam bug reports with the legacy filters and pagination: search by text, filter by type (video/screenshot/replay), origin (capture surface), folder, author, URL, or creation date. Returns Jam metadata including title, origin, author, folder, and timestamps. Each returned Jam carries a url, the share link to hand back to the user unchanged: it carries search attribution.

Input Schema

NameRequiredDescriptionDefault
urlNoFilter by original page URL (partial match, case-insensitive)
typeNoFilter by Jam type
afterNoCursor for forward pagination (Jam ID)
limitNoMaximum number of results to return
queryNoText search query to filter Jams by title or description
authorNoAuthor filter: "me", user name, email, or user ID
folderNoFolder filter: folder name, folder ID, folder short ID, or "root" for unfiled Jams
intentNoIn 15-30 English words, your larger task and why this call helps it. People by role ("a customer"); no argument values or secrets.
originNoFilter by capture surface. native_macos is the macOS app, native_cli is the jam CLI, extension_chrome is the browser extension, recording_link is a shareable recorder link, mobile_ios / mobile_android are the mobile apps.
orderByNoSort order fieldcreatedAt
createdAtNoFilter by creation date: ISO date string or ISO 8601 duration (e.g., "-P7D" for last 7 days)
llm_modelNoYour exact model id from your system prompt, or "unknown". Never guess.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / intent / description
      Previous value: -"In 15-30 words, say what larger task you are working on and why this tool helps it. Refer to people and companies by role (\"a customer\"), and leave out argument values and secrets. Use English. Example: \"Debugging a checkout failure a customer reported, checking which network request returned the 500.\""New value: +"In 15-30 English words, your larger task and why this call helps it. People by role (\"a customer\"); no argument values or secrets."
    • changedInput schema / properties / llm_model / description
      Previous value: -"The exact model identifier you are running as, from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Pass \"unknown\" if you are not certain; never guess."New value: +"Your exact model id from your system prompt, or \"unknown\". Never guess."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by describing returned Jam metadata and the special handling of each Jam's url as a share link to return unchanged.

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 three sentences, front-loads the deprecation warning, and then efficiently covers filters, return values, and the special url handling. There is no unnecessary wording.

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 12-parameter read-only listing tool with no output schema, the description provides enough context: it names the filter dimensions, mentions pagination, and describes the returned metadata and share-link behavior. The schema covers parameter details, so the remaining gap is minor.

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 input schema already documents all 12 parameters in detail. The description summarizes the filter categories and pagination but does not add syntax or format details beyond what the schema provides, making the baseline score appropriate.

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: it lists Jam bug reports using legacy filters and pagination. It also explicitly names the sibling replacement, searchJams, so an agent can distinguish this deprecated tool from the current one.

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

Usage Guidelines5/5

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

The first sentence gives explicit when-not-to-use guidance: 'Deprecated: use searchJams instead.' This directly routes the agent to the correct alternative and makes the legacy status unambiguous.

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

All Jam toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources