Skip to main content
Glama
Sign In

aitrips.io

by io.aitrips
OverviewDiscussionsAdmin

trip_share_create

Create a share link for a trip (owner only). By default this is a PRIVATE link: recipients who open it become collaborators and need an account. Set isPublic: true instead to publish a read-only page that anyone holding the URL can open with no account and no sign-in at all — set that only when the user explicitly wants a page they can hand out publicly, not merely to get around a collaborator limit.

Input Schema

NameRequiredDescriptionDefault
tripIdYesTrip ID
maxUsesNoMaximum number of times link can be used
isPublicNoCreate a public, read-only link anyone with the URL can open without an account, instead of a private collaboration link (default false)
permissionNoPermission level for recipients (forced to VIEWER when isPublic is true)VIEWER
showPhotosNoPublic links only: let anonymous viewers see photo moments in the trip recap, with no uploader name or avatar and no task moments. Refused when isPublic is not also true (default false)
expiresInDaysNoDays until link expires

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / showPhotos
      Added value: +{
+  "default": false,
+  "description": "Public links only: let anonymous viewers see photo moments in the trip recap, with no uploader name or avatar and no task moments. Refused when isPublic is not also true (default false)",
+  "type": "boolean"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / isPublic
      Added value: +{
+  "default": false,
+  "description": "Create a public, read-only link anyone with the URL can open without an account, instead of a private collaboration link (default false)",
+  "type": "boolean"
+}
    • changedInput schema / properties / permission / description
      Previous value: -"Permission level for recipients"New value: +"Permission level for recipients (forced to VIEWER when isPublic is true)"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false); the description adds the behavioral consequences the schema cannot: owner-only authorization, that private-link recipients become collaborators and must have an account, and that public links are read-only and anonymous. These are exactly the side effects an agent must know before invoking.

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?

Purpose and the owner-only constraint are front-loaded, then the mode guidance follows logically. The long em-dash sentence is dense but each clause carries information; minor trimming would be possible but nothing is wasted.

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

Completeness3/5

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

For a 6-parameter mutation tool with no output schema, the description covers authorization and side effects well but never says what is returned (presumably a share URL/token), leaving the agent to guess the response shape. That is the main remaining gap given no output schema exists to compensate.

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, but the description adds meaning beyond the schema for isPublic by spelling out the downstream effects of each mode. It leaves maxUses and expiresInDays entirely to the schema, which is acceptable given full coverage.

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 ('Create a share link for a trip') and immediately narrows scope with '(owner only)'. It also distinguishes the two link modes, which is the key conceptual split an agent needs before choosing it over trip_collaborators_invite or trip_share_list.

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?

Explicitly names the default behavior (private collaboration link) and the alternative mode with a condition: set isPublic only when the user explicitly wants a hand-out public page, 'not merely to get around a collaborator limit.' This is an explicit when/when-not with the misconception preempted.

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

All aitrips.io 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