Telerivet

get_web_app_urls

Read-only

Returns Telerivet web app URL patterns and page details for linking users to features, including functionality not available via the API (sending, contacts, scheduling, statistics, user permissions, and more). Without a query, returns a compact index of all pages (titles and URL patterns); with keywords or a URL path (e.g. "schedule messages" or "/p/abc123/contacts"), returns full details for the matching pages including supported query parameters and available actions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_web_app_urls"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No	Keywords (e.g. "message statistics"), or a web app URL or path (e.g. "/p/abc123/messages") to match a specific page. Omit to get a compact index of all pages.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds the return-shape distinction between the compact index (titles and URL patterns) and full details (supported query parameters and available actions), which is real behavioral context beyond the annotations.

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?

Two sentences, front-loaded with the purpose before the mode rules, and the parenthetical examples are compact and useful. The second sentence is long but each clause (index mode, full-detail mode, what full details contain) carries information an agent needs.

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 carries the return-value burden and does so by describing both response modes and their contents. Combined with annotations covering safety and a fully documented single parameter, nothing essential for correct invocation is missing.

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% and the schema already explains the query parameter, so the baseline is 3. The description adds value by tying the parameter's presence or absence to two materially different response modes, which the schema does not state.

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 ('Returns Telerivet web app URL patterns and page details') and immediately carves out its niche versus API-based siblings with 'including functionality not available via the API'. An agent can tell this is the web-app/page-navigation tool, not an API method tool, 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?

Explicitly defines the two invocation modes: omit the query for a compact index, supply keywords or a path for full details, with concrete examples for each. It does not name an alternative tool or state when another tool would be preferable, so it stops short of a 5.

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

All Telerivet tools Inspect

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

Need Help?