Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dev.to video posts

dev_to_videos_list
Read-onlyIdempotent

Lists Dev.to posts that include a video so you can browse video content by page and limit results; use pagination to collect additional posts.

Instructions

List Dev.to posts that carry a video. Optional inputs: page and limit. Returns a list (use page when paginated).

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dev_to_videos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-1000). Default: 1. Live feeds move as posts are published, so a later page can repeat rows from an earlier one; dedupe by `id`.
limitNoRows per page (1-1000). Default: 30. A page is the same price at any size.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only that the result is a list and that page applies when paginated — the more interesting caveat about live feeds repeating rows across pages lives in the schema, not here. Modest added value beyond annotations.

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?

Two compact sentences with the resource scope front-loaded and the pagination note trailing. The 'Optional inputs: page and limit' clause is mild duplication of the schema but is short enough not to be wasteful.

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?

This is a simple read-only list endpoint with full schema documentation and complete annotations, so little description is required. The one gap is that no output schema exists and the description says only 'Returns a list' without indicating what fields come back, which an agent might want to know.

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%, including detailed notes on the page/limit ranges, dedupe by id, and the context/llm_model/conversation_id fields. The description only restates that page and limit are optional, adding no syntax, defaults, or constraints beyond the schema. Baseline 3 applies.

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 plus a scope qualifier: 'List Dev.to posts that carry a video.' That is enough to separate it from a generic article list, but it never names dev_to_articles_list or explains the subset relationship, so the differentiation is inferred rather than stated.

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 only usage hint is 'use page when paginated,' which is pagination mechanics rather than when-to-use guidance. There is no statement about when to pick this over dev_to_articles_list or dev_to_feed_home_list, and no exclusions; usage is implied by the tool name and scope phrase.

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