Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get AllTrails activity feed

alltrails_get_activity_feed
Read-onlyIdempotent

Retrieve an AllTrails user's activity feed, including recorded hikes and posts. Omit feed to list available feeds, or specify local, timeline, or personal to get items.

Instructions

Get an AllTrails user's activity feed (recorded hikes and posts). Defaults to the signed-in user; pass a userId to target a specific public profile. Without a feed argument this returns the feed DIRECTORY (the available feeds: local, timeline (following), personal (own posts)) — pass feed to get the actual items. Returns slim projections by default; pass view:"full" for the whole records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedNoWhich feed to read: local (nearby activity), timeline (people you follow), personal (own posts). Omit to list the available feeds.
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns { count, hasNextPage, nextCursor, items: [{ type, timestamp, description, user, trail, activity, review }] } — and the no-feed directory as { name, displayName } per feed; "full" returns AllTrails' whole records.
cursorNoOpaque nextCursor from a previous page, for pagination
userIdNoNumeric AllTrails user id. Defaults to the signed-in user.
maxItemsNoMax items per page (server-side)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.9
    • addedInput schema / properties / userId / pattern
      Added value: +"^\\d+$"
  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. Changed2 schema fields changedv2.3.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "description": "Return slim projections instead of the full records (default false)",
-  "type": "boolean"
-}
    • 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, hasNextPage, nextCursor, items: [{ type, timestamp, description, user, trail, activity, review }] } — and the no-feed directory as { name, displayName } per feed; \"full\" returns AllTrails' whole records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior: that a missing feed argument returns a DIRECTORY rather than items, and that output is slim by default with an opt-in to full records. It does not mention permissions or rate limits, which is 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 front-loaded sentences with no filler: identity/scope first, then the userId and feed branching, then the view default. Each sentence carries a distinct decision the caller must make.

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 steps in to explain the two possible return shapes (directory vs items) and the compact/full projection. Pagination via cursor and maxItems is left to the schema, which is adequate, though a top-level note on paging would fully close the loop.

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 coverage is 100% and the schema descriptions already explain feed values, the omit-to-list-feeds behavior, view compact/full shapes, and user id defaults. The description largely restates those semantics rather than adding new detail, so the baseline 3 applies.

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+resource ('Get an AllTrails user's activity feed') and immediately scopes it to 'recorded hikes and posts'. It is clearly distinguishable from siblings like get_profile, list_completed_trails, and list_user_lists.

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 explicit selection rules: omit userId to use the signed-in user, pass it to target a public profile, omit feed to get the directory and pass feed to get items. It doesn't name alternative sibling tools for related data, but the in-tool branching guidance is strong.

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