Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List AllTrails user lists

alltrails_list_user_lists
Read-onlyIdempotent

List saved AllTrails lists for the signed-in user or a specified user ID. Returns compact entries by default; use view:'full' for complete records.

Instructions

List an AllTrails user's saved lists (favorites, custom lists). Defaults to the signed-in user; pass a userId to target a specific public profile. Returns slim { id, name, itemCount, visibility } entries by default (feed an id to alltrails_get_list_items); pass view:"full" for the whole records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns { count, lists: [{ id, name, itemCount, visibility }] }; "full" returns AllTrails' whole list records.
userIdNoNumeric AllTrails user id. Defaults to the signed-in user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.1.9
    • addedInput schema / properties / userId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns { count, lists: [{ id, name, itemCount, visibility }] }; \"full\" returns AllTrails' whole list records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv3.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety is covered; the description adds real value on top by specifying the default response shape (slim { id, name, itemCount, visibility }) and that userId only resolves public profiles. It does not cover pagination or rate-limit behavior for a feed-style list, leaving a minor gap.

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?

Three tight sentences with the core purpose, targeting rule, and return-shape choice front-loaded in that order. Every clause carries information the agent needs and none is padding.

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 no output schema, the description correctly takes on the burden of explaining return values and does so for both view modes, while annotations handle safety. The only unaddressed element is pagination/limits for potentially long list sets, which keeps it from a 5.

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 earns an extra point by adding the 'public profile' constraint on userId and by restating the compact-vs-full tradeoff in terms of the actual returned fields. It repeats the default values the schema already documents but adds a genuine targeting restriction.

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?

States a specific verb and resource ('List an AllTrails user's saved lists') and immediately scopes it with examples ('favorites, custom lists'). It clearly separates itself from alltrails_get_list_items, which it points to for the item-level detail rather than duplicating.

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 clear selection context: omit userId for the signed-in user, pass userId to target a public profile, and use alltrails_get_list_items if you need the contents of a returned id. It stops short of stating any exclusion or when-not-to-use case, so it falls just under the 'explicit when/when-not' bar.

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