Skip to main content
Glama

project_view_urls

Read-onlyIdempotent

Get the public live URLs for a project. prod is the verified custom domain when one exists; prod_fallback is the public *.somewhere.site URL and always serves the latest live deploy.

Example:

{ "project_id": "my-saas" }
// Returns: {
//   "prod": "https://app.yourcompany.com",          // null if no custom domain
//   "prod_fallback": "https://my-saas.somewhere.site",
//   "prod_version": 12,
//   "has_custom_domain": true
// }

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": {
      "project_id": "<project_id>"
    },
    "name": "project_view_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID, subdomain, or 'default'.

Output Schema

NameRequiredDescriptionDefault
okNo
dataNo
errorNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds real behavioral context beyond that by noting `prod` is null when no custom domain exists and that `prod_fallback` always serves the latest live deploy. It does not mention permissions or eventual consistency, keeping it short of a 5.

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 is front-loaded in one sentence, followed by field definitions and a compact example. The JSON-with-comments example is slightly bulky but earns its place by showing the exact return shape; nothing is redundant prose.

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?

For a one-parameter read tool with an output schema and annotations already present, the description covers everything needed: what it returns, the semantics of each field, and the null case. Nothing required to call or interpret it 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 coverage is 100% and the single `project_id` parameter is already described as accepting an ID, subdomain, or 'default'. The example echoes that format but adds no new constraint or meaning beyond the schema, 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 ("Get the public live URLs for a project") and immediately disambiguates the two URL kinds it returns, `prod` vs `prod_fallback`. No sibling in the list does this, so an agent can select it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the meaning of each returned URL (custom domain vs always-latest fallback), which helps interpret results, but gives no when-to-use/when-not guidance and names no alternative. Usage is only implied — e.g., after a deploy to retrieve the live address.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources