finn-seller-mcp

by ML-senior

Overview Schema Source Related Servers Discussions Admin

Python

Local

list_drafts

List saved ad drafts and their finn.no status when logged in, showing draft, active, missing, or unchecked states.

Instructions

List local drafts.

    `status` is checked against finn.no ("Mine annonser") when logged in:
    `remote_state` is finn.no's own state (DRAFT, ACTIVE ...), "missing" if
    the ad no longer exists there, or absent if it could not be checked.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral load. It does disclose a valuable trait: a per-item remote check against finn.no's "Mine annonser" that only happens when logged in, plus the tri-state result (real state, "missing", or absent when unchecked). It says nothing about whether this is a read-only operation, whether the remote check is slow/rate-limited, or what happens when the check fails wholesale.

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?

The purpose is front-loaded in a single short sentence, followed by the one nuance that matters. The second part is a fragment with stray indentation and reads awkwardly, but no sentence is wasted.

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 zero-parameter list tool with an output schema, the definition covers the essential unknown: that `remote_state` can be a real state, "missing", or absent depending on login and network check. Remaining gaps (local storage scope, effect of failed checks) are minor given the output schema documents the return shape.

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?

The tool takes zero parameters, so there is no parameter semantics burden; baseline is 4. The description's mention of `status` and `remote_state` refers to output fields (documented by the output schema) rather than inputs, so it adds no confusion on the input side but also contributes nothing there.

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?

"List local drafts" states a specific verb and a scoped resource (local, as opposed to finn.no-hosted ads), which lets an agent distinguish it from network-oriented siblings like my_ads or search_finn. It stops short of naming any sibling explicitly, so the differentiation is inferable 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 phrase "when logged in" implies a precondition for the richer output, and "local drafts" implies the scenario (reviewing work-in-progress before pushing/publishing). However, there is no explicit when-to-use vs my_ads/get_listing guidance and no statement of when-not to use it.

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