Skip to main content
Glama

Visibility Genies

Create a client report link

create_report_share

Creates a private link to the project's client report for the user to send to their client. The link opens this project's client report to anyone who has it, without an account: its scores, what changed, the actions and any connected ad results, kept up to date. Call it only when the user asks for a link, with confirm: true; without it, nothing is created and the answer explains what the link would show. One link per project: a second needs regenerate, which ends the first. The link is ended in Project settings, Report links. Free.

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": {
      "projectId": "<projectId>"
    },
    "name": "create_report_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNotrue only after the user has asked for the link and understood that anyone who has it can open the report. Without it nothing is created.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
regenerateNoReplace the project's current link: the old one stops working. Only when the user asks.
expiresInDaysNoDays until the link stops working, 90 unless the user says otherwise.

Output Schema

NameRequiredDescriptionDefault
urlNo
metaNo
createdYes
expiresInDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the link is publicly readable without an account, contents include scores/changes/actions/ad results, one link per project and a second requires regenerate which kills the first, revocation happens in Project settings > Report links, and it is free. Annotations only cover readOnly/openWorld/destructive, so this is a real addition; the only minor gap is nothing about expiry defaults beyond 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 with the outcome, then the access model, then the call condition and the one-link rule. Dense but every sentence carries information; the 'without it, nothing is created' clause is slightly redundant with the schema's confirm description.

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 mutating, publicly-exposing tool it covers the disclosure risk, the user-consent gate, the single-link constraint, reversal path, and cost. With annotations and an output schema present, nothing an agent needs 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%, so all four parameters are already documented in the schema. The description reinforces the confirm gate and the one-link/regenerate relationship but adds no syntax or format detail the schema does not already 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 ('Creates a private link to the project's client report') plus the audience and access model, which cleanly separates it from the read-only sibling get_client_report.

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?

Gives an explicit gating condition ('Call it only when the user asks for a link, with confirm: true'), states what happens without it, and covers the regenerate case when a link already exists. An agent knows both when to call and when not to.

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