Skip to main content
Glama

flickr_open

Open a Flickr page in your signed-in Cloud Browser to manage photos, albums, tags, privacy, comments, and groups, defaulting to the login page for account access.

Instructions

Open a Flickr page in your signed-in Cloud Browser (default https://identity.flickr.com/login) to work with organize photos, albums and tags, review privacy and manage comments and groups.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://identity.flickr.com/login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It does add one valuable behavioral fact — the browser session is signed-in, so authenticated content is reachable — but it omits what navigation does to an already-open page, failure modes for invalid URLs, and whether this blocks until load completes.

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?

One sentence, front-loaded with the action and the default target. The trailing laundry list of Flickr tasks is mildly padded but not confusing.

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?

For a one-optional-parameter navigation tool with no output schema, the description conveys what it does, the default destination, and the authenticated-session context. Enough to call it correctly; only edge-case behavior is missing.

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?

There is a single optional parameter with 100% schema coverage, so the schema already documents the url field and its default. The description only restates the default URL and adds no format or constraint detail beyond it, which matches the baseline 3 for a fully-covered schema.

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 opens with a specific verb and resource — 'Open a Flickr page in your signed-in Cloud Browser' — and names the default URL, so the agent can tell this is a navigation tool distinct from flickr_read or flickr_click. The trailing list of tasks ('organize photos, albums and tags, review privacy...') broadens rather than sharpens the purpose.

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 intent is to get a page loaded in the browser before doing something with it. There is no explicit 'call this before flickr_click/flickr_type' statement, no when-not guidance, and no mention of what to do if a page is already open.

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