Perspective AI

perspective_get_preview_link

Read-onlyIdempotent

Returns a shareable URL that opens the perspective in preview mode, so you (or a teammate) can have a sample conversation with it before deploying.

Behavior:

Read-only. The same stable preview URL every time for a given perspective; the link does not expire.
Conversations started from this URL are preview conversations and do NOT count toward the workspace's quota.
Anyone with the link can start a preview conversation, even unauthenticated — treat as semi-public.

When to use this tool:

After perspective_create or perspective_update, to manually verify the perspective's behavior before going live.
To share a preview link with a teammate for review.

When NOT to use this tool:

For production deployment — use perspective_get_embed_options, which returns embed snippets and a public share link whose conversations count toward quota.
To inspect existing real conversations — use perspective_list_conversations / perspective_get_conversation.

Typical flow:

perspective_create → design
perspective_get_preview_link → test
perspective_update → refine
perspective_get_embed_options → deploy

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "perspective_id": "<perspective_id>"
    },
    "name": "perspective_get_preview_link"
  }
}

Input Schema

Name	Required	Description	Default
`workspace_id`	Yes	Workspace ID (from workspace_get_default or workspace_list) or workspace slug (uniqueName)
`perspective_id`	Yes	Perspective ID (from perspective_list or perspective_create)

Output Schema

Name	Required	Description	Default
`error`	No
`preview_url`	Yes	URL to preview the perspective (test mode)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026
- addedInput schema / properties / perspective_id / maxLength
```
Added value: +128
```
- addedInput schema / properties / workspace_id / maxLength
```
Added value: +128
```

Changed2 schema fields changedSep 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedApr 29, 2026

changedOutput schema / properties / preview_url / description

Previous value: -"URL to preview the interview (test mode)"New value: +"URL to preview the perspective (test mode)"

First observedApr 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely new traits: stable non-expiring URL, preview conversations exempt from quota, and semi-public access for unauthenticated holders. These are quota, security, and lifecycle facts an agent could not infer from the schema.

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 one-line summary followed by clearly labeled sections; the quota and semi-public warnings are high-value. Slight redundancy between the 'When to use' bullets and the 'Typical flow' steps keeps it from a 5.

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?

Output schema exists so return-value detail is unnecessary, and the description still covers lifecycle, access model, and quota implications. Nothing an agent needs to call this correctly is missing.

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 description coverage is 100% and both parameters already document their source tools (workspace_get_default/workspace_list, perspective_list/perspective_create). The description adds nothing parameter-specific, 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 and resource: 'Returns a shareable URL that opens the perspective in preview mode.' The preview-mode qualifier immediately separates it from perspective_get_embed_options and the other perspective tools.

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?

Explicit when-to-use (verify after create/update, share with teammate) and when-NOT-to-use with named alternatives (perspective_get_embed_options for deployment, perspective_list_conversations / perspective_get_conversation for real conversations). A numbered flow ties the siblings together.

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

All Perspective AI 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.