Skip to main content
Glama

flickr_read

Reads the current Flickr page to extract visible text and numbered interactive elements, so you can identify links, buttons, and fields before taking action.

Instructions

Read the current Flickr page: its text and numbered buttons, links and fields.

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": "flickr_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full load. It does disclose the shape of the return content (text, numbered buttons, links, fields), and the phrase "numbered buttons" usefully hints that elements are indexed for later targeting. However, it says nothing about whether a page must already be open, how large pages are truncated, or whether reading has any side effects.

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 front-loaded sentence with no filler; the resource and the returned content are stated in one pass and nothing is redundant.

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?

For a simple, annotation-free read tool with one optional parameter and no output schema, the description covers purpose and return contents adequately but omits prerequisite state (an open page) and any note about output limits, leaving the agent to discover them by trial.

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% and the single optional `element` parameter is already described in the schema as "Read only inside this element." The description adds no additional meaning about scoping or how element indices are obtained, so the baseline of 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 pairs a specific verb ("Read") with a specific resource ("the current Flickr page") and enumerates what comes back: text, numbered buttons, links and fields. That clearly separates it from sibling action tools like flickr_click or flickr_type, though it never explicitly contrasts itself with state tools like flickr_status or flickr_guide.

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?

The word "current" faintly implies the tool operates on whatever page is loaded, but there is no explicit when-to-use guidance, no prerequisites (e.g. a page must be open), and no mention of alternatives such as flickr_guide or flickr_status when a different view is wanted.

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