Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Behance freelance briefs

behance_freelance_briefs_list
Read-onlyIdempotent

List current Behance freelance briefs one page at a time, using limit and cursor to continue paginated results and find relevant freelance projects.

Instructions

List current Behance freelance briefs, 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_freelance_briefs_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

A3.5/5.0
Behavior3/5

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

The annotations already establish that the operation is read-only, idempotent, and non-destructive. The description adds page-at-a-time retrieval and a list result, but otherwise provides little behavioral context, such as what "current" means or what information each brief contains.

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 and the three short sentences are easy to scan. The separate optional-input sentence is largely redundant with the schema, and the final parenthetical could be integrated more cleanly into the pagination statement.

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 simple read-only paginated list, the description, fully documented input schema, and safety annotations provide enough information to invoke the tool correctly. With no output schema, however, "Returns a list" leaves the brief fields and pagination envelope unspecified, and sibling-selection guidance is also absent.

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 schema already documents the limit bounds and default as well as the cursor's source and same-list restriction. Naming `limit` and `cursor` as optional and repeating cursor usage adds little meaning beyond those structured fields, so the high-coverage baseline 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 opening phrase gives a specific verb and resource—listing current Behance freelance briefs—and "one page at a time" clarifies the retrieval scope. It does not explicitly distinguish this operation from the singular brief getter or other brief-related siblings.

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 instruction to "use cursor when paginated" provides concrete continuation guidance, while "current" implies a browsing context. There is no explicit when/when-not guidance or named alternative to help choose among sibling tools.

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