Skip to main content
Glama
Sign In

Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram

by ai.bowmark
OverviewDiscussionsAdmin

List the user's pages (jigs)

jig_list
Read-onlyIdempotent

The jigs this user has, newest change first: id, slug, title, the built-in it started from, and when it last changed. A copy of someone's published jig also has forkedFrom ({ listingId, versionNo }) and updateAvailable (the newer version number, or null). Call it when the user mentions a page they made before ("my YouTube feed", "that dashboard"), then reopen it with jig_open({ jigId }) instead of building a new one. When updateAvailable is set, tell the user and offer to update it (jig_pull_update).

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okNoFalse on an error.
jigsNoEvery jig this account owns.
messageNoWhy the call failed, when `ok` is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "jigs": {
+      "description": "Every jig this account owns.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "forkedFrom": {
+            "description": "The published listing it was copied from."
+          },
+          "jigId": {
+            "description": "The jig's id — pass it to every other `jig_*` tool.",
+            "type": "string"
+          },
+          "slug": {
+            "description": "The jig's short name in its URL.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "template": {
+            "description": "The built-in it started from, if any.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "The page's title (fenced text when the jig is a copy of someone else's)."
+          },
+          "untrusted": {
+            "description": "Present when this jig is a copy of someone else's: who wrote it, and how to treat its text."
+          },
+          "updateAvailable": {
+            "description": "Whether that listing has a newer version."
+          },
+          "updatedAt": {
+            "description": "When it last changed (ISO 8601).",
+            "type": "string"
+          },
+          "version": {
+            "description": "The jig's version; it goes up by one on every change.",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "description": "Why the call failed, when `ok` is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "False on an error.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely non-structured behavior: result ordering, and the conditional shape of `forkedFrom` ({ listingId, versionNo }) and `updateAvailable` (version number or null) that only appear on forked copies. It stops short of noting pagination or result-size limits, which matters for a full listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what is returned, then the conditional fork fields, then the usage trigger, then the follow-up action — a sensible ordering with no filler sentences. The per-field enumeration overlaps somewhat with the existing output schema, so a small amount of the text is restating structured data.

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

Completeness5/5

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

With zero parameters, rich annotations, and an output schema carrying return values, the description covers everything an agent still needs: what the list is, how it is ordered, which fields are conditional, and what to do next. No material gap remains for a read-only listing tool.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning to add. The only parameter referenced (`jigId`) belongs to the follow-up `jig_open` call, which is framed usefully but is not this tool's input.

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?

Uses a specific verb and resource ('The jigs this user has') and enumerates exactly what each entry contains (id, slug, title, source built-in, last-changed time), plus ordering ('newest change first'). That is enough for an agent to distinguish this enumeration tool from jig_get, jig_search, or get_library without opening a schema.

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?

Gives a concrete trigger ('when the user mentions a page they made before', with example phrases) and a clear follow-up chain: reopen with `jig_open({ jigId })` rather than rebuilding, and offer `jig_pull_update` when `updateAvailable` is set. It does not state when to prefer a sibling lookup tool (jig_get/jig_search) instead of listing everything, so the exclusion side is incomplete.

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

All Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram 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