Skip to main content
Glama
Sign In

MemoryBrain

by ai.memorybrain
OverviewDiscussionsAdmin

Leer un tablero de Pinterest

read_pinterest
Read-only

Lee un tablero o un perfil PÚBLICO de Pinterest (sus últimos 25 pines): título, texto, enlace y URL de la imagen de cada pin, y te pasa las imágenes de unos pocos (count, máximo 6, desde offset) para que las veas. No guarda nada. Úsala cuando quiera darle su gusto visual desde Pinterest; antes, carga la skill gusto-visual con get_skill. Para ver los siguientes, vuelve a llamar con offset = next.

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": {
      "url": "<url>"
    },
    "name": "read_pinterest"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLa URL del tablero (pinterest.com/usuario/tablero) o del perfil.
countNoCuántas imágenes pasar (4 por defecto).
offsetNoDesde qué pin pasar imágenes (0 por defecto).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description reinforces this with 'No guarda nada', which matters for an agent deciding whether the call has side effects. It also discloses the 25-pin cap and the split between full metadata and a limited image payload. It says nothing about failure modes (private/deleted boards) or rate limits, 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.

Conciseness4/5

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

Front-loaded with the core action and result, then prerequisites and pagination. It is a single dense paragraph with stacked parentheticals ('count, máximo 6, desde offset'), which is efficient but slightly harder to scan than a short structured layout.

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?

There is no output schema, so the description carries the return contract, and it does: the metadata fields, the image-passing behavior, and the 25-pin window. Combined with the prerequisite and pagination instructions, an agent has everything needed to invoke it correctly on the first try.

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 100%, so the baseline is 3. The description does add one genuinely non-schema fact — that pagination continues with offset = next — and clarifies that count controls how many images are passed rather than how many pins are listed, but the rest restates the schema.

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 (read a PUBLIC Pinterest board or profile) plus scope (last 25 pins) and enumerates what is returned: title, text, link, image URL. No sibling tool covers Pinterest, and the get_skill prerequisite makes the boundary with gusto-visual explicit.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when you want to give it your visual taste from Pinterest'), a mandatory prerequisite step (load gusto-visual via get_skill first), and the exact continuation rule (call again with offset = next). The PUBLIC qualifier implicitly excludes private boards.

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

All MemoryBrain 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