YokTez MCP

List Recent Yok Tez

list_recent_yok_tez

List recent YÖK theses without a search keyword. Use modes to fetch the latest 15-day additions or the current year's corpus, with pagination support.

Instructions

List recent YÖK theses without a search keyword.

Calls YÖK's TezIslemleri endpoint (islem=7 or islem=8) and returns the same result shape as search_yok_tez_detailed. This is the ONLY way to enumerate recent theses since the regular search endpoint requires a keyword.

Useful for:

Monitoring new theses added to YÖK each week (SON_15_GUN)
Browsing the current year's full corpus (BU_YIL)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Which curated list to fetch. SON_15_GUN: ~2-3K theses uploaded to YÖK in the last 15 days (useful for monitoring new additions; thesis publication year can vary). BU_YIL: all theses with the current publication year (e.g. ~100K+ for 2026, but YÖK caps the visible batch at ~2000).	7
`page`	No	Page number of the results.
`results_per_page`	No	Maximum number of results per page.

Output Schema

TableJSON Schema

Name	Required	Description
`theses`	No	List of found theses summaries.
`total_pages`	No	Total number of pages available based on results_in_batch and limit_per_page.
`current_page`	Yes	The current page number of the search results.
`error_message`	No	Error message if the search failed or no results were found.
`results_in_batch`	No	Number of results actually returned in the current HTML batch. YÖK caps this at ~2000 even when total_results_found is larger.
`total_results_found`	No	Total number of results found as reported by YÖK.
`query_used_parameters`	No	The parameters used for this search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A4.8/5.0

Behavior4/5

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

No annotations are provided, so the description carries the transparency burden. It discloses the actual endpoints called, the result shape relative to another tool, and the visible batch cap in the mode parameter. It does not explicitly state side effects or auth requirements, but the listing operation is clearly non-destructive.

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

Conciseness5/5

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

The description is well-structured and concise, using short paragraphs and bullet points to convey purpose, endpoint information, and use cases without unnecessary fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists, the description appropriately focuses on invocation context, endpoint behavior, and use cases. It also clarifies important caveats like the result shape and batch cap, making it complete for an agent to decide when to call this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers all parameters, and the description enriches each one meaningfully: mode explains SON_15_GUN vs BU_YIL and the ~2000 cap, while page and results_per_page are clearly defined with defaults and limits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool lists recent YÖK theses without a search keyword, using a specific verb and resource. It also distinguishes itself from search_yok_tez_detailed by noting the regular search endpoint requires a keyword.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains when to use the tool, names the underlying endpoints (islem=7/8), states it is the only way to enumerate recent theses, and provides concrete use cases (SON_15_GUN and BU_YIL).

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

Deploy Server