Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Behance featured projects

behance_featured_list
Read-onlyIdempotent

List featured Behance projects with their cover images and publish dates so you can browse what the creative platform is currently highlighting.

Instructions

List the current featured Behance projects with their covers and publish dates. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that covers and publish dates come back and that the list reflects 'current' featured content. It says nothing about pagination, result count, ordering, or whether the feed changes between calls despite idempotentHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The first sentence is well front-loaded and informative. The trailing 'Returns a list.' is redundant with 'List' and earns no place, leaving the definition thin for the amount of behavioral detail an agent might want.

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 read-only list with full annotation coverage and no output schema, the description covers the basics: what is listed and which fields accompany each item. It omits practical call context such as result volume, pagination, and ordering, so an agent still cannot predict the shape of the response beyond 'a list of projects with covers and dates'.

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%, so all three parameters (context, llm_model, conversation_id) are already documented in detail, including the note about echoing conversation_id. The description adds no parameter meaning of its own, which is acceptable at this coverage level since these are generic plumbing parameters rather than tool-specific filters.

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 ('List the current featured Behance projects') plus the fields returned (covers and publish dates), which distinguishes it from sibling lookups like behance_project_get or behance_profile_projects_list. It stops short of explicitly naming which sibling to prefer, but the scope is unambiguous.

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?

There is no when-to-use guidance, no exclusions, and no pointer to alternatives such as behance_projects_recent_list, which an agent could easily confuse with 'current featured'. The word 'current' hints at freshness but does not say how this differs from a recent-projects listing.

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