Skip to main content
Glama

Minik Günlük

List Minik Günlük videos

list_videos
Read-onlyIdempotent

List short Minik Günlük videos (Turkish): videos for parents on the Minik TV parents page (https://minikgunluk.com.tr/minik-tv/veliler, e.g. nursery adjustment, sleep, screen time, medicine tracking) and app introduction videos. Returns title, description, page URL (and MP4 URL where available). Optional keyword filter. Always show the page URL. TR: Veliler için kısa videolar ve uygulama tanıtım videoları; ör. query "uyku", "ilaç", "kreşe uyum".

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 keyword. / İsteğe bağlı anahtar kelime.
topicNoSame as query (kept for compatibility). / query ile aynı.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real context by enumerating what comes back (title, description, page URL, MP4 URL where available) and imposing an output rule that the page URL must always be shown. It does not mention result limits or pagination, which is the remaining gap.

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?

Purpose and scope are front-loaded in the first clause, and the mandatory 'Always show the page URL' rule is short and actionable. The trailing Turkish sentence partly restates the opening, which is mild redundancy, though it does add localized example queries.

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

Completeness4/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 correctly takes on the return-value burden by listing the returned fields, and annotations already cover the safety profile for this read-only list. What remains unspecified is result volume or whether any paging applies, which matters for a listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by giving concrete example keyword values ('uyku', 'ilaç', 'kreşe uyum') that tell the agent what lexical space the filter accepts. It also notes the valid Turkish-versus-English keyword expectation, though it does not restate the query/topic aliasing beyond what the schema already says.

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 description gives a specific verb and resource ('List short Minik Günlük videos') and scopes the content precisely: parent-facing videos on the Minik TV parents page plus app introduction videos, with parenthetical topic examples. The resource type (videos) is inherently distinct from the sibling guide tools, but no sibling is named, so it stops short of explicit differentiation.

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?

Usage is only implied: the reader infers 'call with no args to browse all videos, or pass a keyword to filter.' There is no statement of when to prefer this over search_parent_guides or get_parent_guide, and no exclusions or prerequisites. The 'Always show the page URL' line is output guidance rather than selection guidance.

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