Skip to main content
Glama

Read an Artifact's analytics

read_artifact_analytics
Read-onlyIdempotent

Who opened a document or page you own, edit, or published: views, signed-in readers, and which Version each last opened. On a company document or page it names every member who can open it, with their opens and, for a document, whether they read the latest version; company admins read it for every company item. Use it to answer 'who has read the policy?' or 'has the team opened the dashboard?'. A reader list carries email addresses, so answer the question asked rather than pasting it.

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": {
      "artifact_id": "<artifact_id>"
    },
    "name": "read_artifact_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifact_idYesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….

Output Schema

NameRequiredDescriptionDefault
typeNo
readersYesCompany items only; null on a personal one.
versionsNo
view_countYes
artifact_idYes
last_viewed_atNo
unique_viewersYes
published_version_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the authorization model (you must own, edit, or have published the item; company admins see every company item) and what varies by item type (version read status only applies to documents). It also flags that the response carries email addresses and advises not to paste the list, which is material behavioral context an agent would otherwise not have.

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?

The scope and metrics are front-loaded in the first sentence, followed by the company-item behavior and concrete use cases. Every sentence carries information, though the admin/company clause and the follow-up permission sentence overlap somewhat and could be tightened.

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?

With an output schema present, return shape needn't be explained, and the single parameter is fully covered by the schema. The description covers what remains: who can see what, how results differ by item type, and the privacy handling of reader emails — enough for an agent to call and use it correctly.

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?

The schema fully documents the single artifact_id parameter, including its pattern and how to derive it from a link, so the schema does the heavy lifting. The description's reference to 'a document or page you own' adds only indirect context about which ids resolve successfully; no additional format or parsing detail is offered beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause gives a specific verb and scope: 'Who opened a document or page you own, edit, or published: views, signed-in readers, and which Version each last opened.' The tool's coverage (personal items vs. company-wide member lists) is stated concretely. It stops short of naming a sibling, so an agent must infer that presentation analytics live elsewhere.

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?

The description supplies concrete triggering questions ('who has read the policy?', 'has the team opened the dashboard?') and states the ownership/permission preconditions for getting personal vs. company-wide results. It does not explicitly exclude or redirect to alternatives such as presentation or thread analytics, so routing is left to inference.

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