Skip to main content
Glama
Sign In
Senja MCP Server

Senja MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read one testimonial

get_testimonial
Read-onlyIdempotent

Read one exact Senja testimonial with native video metadata and public/dashboard links. Use it to retrieve a specific testimonial by ID for review, display, or verification.

Instructions

Read one exact testimonial, including native video metadata and public/dashboard links.

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": {
      "testimonial_id": "<testimonial_id>"
    },
    "name": "get_testimonial"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoExact configured private account profile label; not a tenant or provider account ID.
testimonial_idYesExact testimonial ID. No slash, traversal or arbitrary URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety and access profile is covered. The description adds that the read includes native video metadata plus public/dashboard links, which is useful context about what it returns, but says nothing about permissions, error cases, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the action and resource and wastes nothing. Appropriately sized for a two-parameter read tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety and schema at 100% coverage, the core is complete. But the description hints at a rich return payload (native video metadata, public/dashboard links) with no output schema, so it stops short of telling the agent what it will receive or when this read is preferable to list_testimonials.

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 the two parameters are fully documented in the schema itself, including the account label caveat and the traversal guard on testimonial_id. The description adds no param-level meaning, which matches the baseline when the schema does the heavy lifting.

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?

States a specific verb ('Read') and resource ('one exact testimonial') with singular scope, distinguishing it from the sibling list_testimonials. However, it doesn't name or contrast any alternative for retrieving a testimonial by ID, so sibling differentiation is only implicit.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives. The description never signals that list_testimonials is for enumeration while this is for a single lookup, leaving the agent to infer routing.

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

Deploy Server

Other Tools