Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List recent Behance projects

behance_projects_recent_list
Read-onlyIdempotent

Retrieve recently published Behance projects in paginated batches; set a page limit or pass the previous response's cursor to continue through the list.

Instructions

List recently published Behance projects, one page at a time. Optional inputs: limit and cursor. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page, 1 to 500. Default: 100.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same list.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine pagination behavior ("one page at a time", cursor reuse across pages), which is useful, but it omits ordering guarantees, page-size defaults, and rate/scope constraints that matter for an open-world listing.

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?

Three short sentences, front-loaded with the core purpose, with no filler. The closing parenthetical "(use cursor when paginated)" is mildly redundant with the cursor schema description but is not a real cost.

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?

There is no output schema, so the description must say something about returns, and it does (a list, paginated via cursor) without exposing the response shape such as the nextCursor field name. For a simple read-only listing with full schema coverage, that leaves only minor gaps, though the pagination contract is thinner than ideal.

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 the schema already explains limit bounds and that cursor comes from `page.nextCursor`. The description only restates that these two are optional, adding no format or interaction detail beyond the schema and omitting any mention of the required context/llm_model/conversation_id fields.

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 recently published Behance projects" gives a specific verb plus resource and adds the scope qualifier "recently published". It does not, however, distinguish itself from close siblings such as behance_featured_list or behance_profile_projects_list, which an agent must otherwise infer.

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 description gives no when-to-use context, no exclusions, and never names an alternative for a non-recent or filtered listing. The only operational hint is "use cursor when paginated," which is a parameter note rather than guidance on selecting this tool.

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