Skip to main content
Glama

HelloBooks AI Agents MCP Server

list_videos

Read-only

List HelloBooks product videos curated on the marketing site (homepage demo + feature walkthroughs) and the official @hellobooksai YouTube channel link. Each video returns title, description, category, watch URL, embed URL and thumbnail. Filter by category (demo / features / overview), featuredOnly, or free-text query. Use this when a user asks for a demo, walkthrough or video. Note: this is the curated set, not a live mirror of every channel upload — the response includes the channel URL for the full catalog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional substring match against video title + description.
categoryNoFilter to one video category (demo, features, overview).
featuredOnlyNoIf true, only return videos flagged as featured on the marketing site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: what each result contains (title, description, category, watch URL, embed URL, thumbnail) and, importantly, the curation caveat that results are not a live channel mirror. It omits pagination/size behavior, which keeps it below 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.

Conciseness5/5

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

Three sentences, front-loaded with the resource and scope, then the return shape, then filters, then the usage trigger and caveat. No filler, and the return-field enumeration is justified because no output schema exists.

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 zero-required-parameter read-only list tool with no output schema, the description covers purpose, result shape, filter options, the usage trigger, and the curated-vs-live limitation. An agent can decide to call it and interpret the response without further information.

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 every parameter is already documented in the schema, including the enum values and the substring-matching semantics. The description restates the three filter modes ('category (demo / features / overview), featuredOnly, or free-text query') without adding syntax, combining behavior, or defaults beyond what the schema says. Baseline 3 is the correct ceiling here.

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 ('List HelloBooks product videos curated on the marketing site') and immediately bounds the scope with concrete content types (homepage demo + feature walkthroughs, plus the YouTube channel link). It also pre-empts the most likely confusion by distinguishing the curated set from a live mirror of every channel upload.

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?

Gives an explicit trigger: 'Use this when a user asks for a demo, walkthrough or video.' The closing note explains the boundary condition (curated set, channel URL in response for the full catalog), which effectively says when this tool is not sufficient on its own. No named sibling alternative is offered, but none of the listed siblings appears to cover videos.

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.