Skip to main content
Glama
Sign In

blink artifact

by com.blinkbrosai
OverviewDiscussionsAdmin

Get artifact analytics

artifact_analytics
Read-only

View statistics of an artifact you own: { totalViews, anonymousViews, uniqueViewers, days (last 30 UTC days, each { day, views, anonymous }), viewers (up to 100, newest first, each { userId, name, lastSeenAt ISO, views }) }. Names are people who viewed the artifact; anonymous viewers are counts only. Your own views and agent reads are not counted.

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": {
      "id": "<id>"
    },
    "name": "artifact_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

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?

Beyond the readOnly/destructive annotations, the description discloses meaningful behavior: the 30-day UTC window, the 100-viewer cap with newest-first ordering, that names map to viewers while anonymous entries are counts only, and that the owner's own views and agent reads are excluded. That is real counting-semantics context an agent cannot get from annotations; only lower-level details (rate limits, errors for non-owned ids) are absent.

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 response shape is front-loaded in the first sentence, followed by two short clarification sentences about names, anonymous counts, and exclusions. Dense but every clause carries information; the inline brace-notation is slightly heavy but functional.

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 no output schema, the description fully carries the return contract (totalViews, anonymousViews, uniqueViewers, days array, viewers array with fields and ordering) plus the exclusion rules that affect interpretation. An agent has everything needed to call and read the result 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?

Schema coverage is 0%, so the schema alone gives no meaning for 'id'. The description only indirectly conveys it is the artifact identifier via 'an artifact you own'; it never states the expected id format or what happens with an id you don't own.

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+resource ('View statistics of an artifact you own') and scopes it to a single artifact, which clearly separates it from siblings like get_artifact (content) or list_artifacts (enumeration). An agent can identify the tool without opening the schema.

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?

The phrase 'an artifact you own' implies the ownership precondition, but there is no explicit statement of when to call this versus get_artifact or list_artifacts, and no exclusion guidance. Usage is inferable but not spelled out.

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

All blink artifact toolsInspect
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